characteristics of REST WSs

WSs based on REST architecture encapsulate a lot of functionality. The characteristics of REST are as follows

Client-Server Pull-based Interaction Style

• Pull-based interaction between the client and server means that the client actively requests changes on the server side, based on some time interval. The client will not automatically get recent changes about some activity continuously changing on the server side.
• In this interaction, the user interface matters are kept separate from the data storage matters, thereby enhancing portability across various platforms.

Layered Components

• Intermediaries, such as proxy servers, cache servers, gateways, etc. can be inserted between clients and resources to support performance, security, etc.
• This existence of proxy permits increasing client functionality by downloading and executing code in applets.
• REST system is divided into layers, and each layer cannot see the functionality of the other layers, except that of the adjacent layers.

Cache

• To improve network efficiency responses must be capable of being labeled as cacheable or non-cacheable.
• Responses should be able to cache. The benefit of caching is that it removes the need for further interaction and results in greater efficiency and scalability.

Stateless

• As per the REST architecture, the server does not store any state about the client session on the server side. This restriction is called Statelessness.
• Each request from client to server must contain all of the information necessary to understand the request, and cannot take advantage of any stored context on the server. Session state is therefore kept entirely on the client.
• Client is responsible for storing and handling all application state related information on client side.

Uniform Interface

• All resources are accessed with a generic interface (e.g., HTTP GET, POST, PUT, DELETE).

Named Resources

• The system is comprised of resources which are named using a URL.

Interconnected Resource Representations

• The representations of the resources are interconnected using URLs, thereby enabling a client to progress from one state to another.
• Client state can be changed from one to another.