RESTFul means Representational State Transfer. In a REST approach, servers communicate with clients using stateless connections. All the information about the state of the interaction
between the two is encoded into the requests and responses between them. Long-term state is kept on the server as a set of identifiable resources. Clients access these resources using a well-defined set of resource identifiers . REST distinguishes the content of resources from the presentation of that content. RESTFul technique abandoned server based sessions.
Difference Between RESTFul technique and SOAP/XML-RPC system……..
- Clients in a RESTFul system are required to submit all the information which are necessary to process a request in a header.
- In SOAP (Simple Object Access Protocol) or XML-RPC system, the body of the message need not to be examined for the server in order to route it to the proper segment of the code.
Extra Features of RESTFul technique
1. Resources and requirement of a uniform interface :
Resources are the heart of the four requirements of the RESTFul uniform interfaces –>
- Resource identification
- Resource manipulation via representation
- Self descriptive messaging
- Use of hypermedia as the engine of application state.
2. Layerd systems :
The layered system requires that each component in the chain between client and server knows about only its immediate neighbors.
3. Code-on-demand :
With this feature clients of a RESTFul application can be modified on-the-fly by downloading only the additional functional code from the server. [ It is a topic that has not yet
been addressed in the Rails community, though it opens up possibilities of client extensibility
that may make it worthwhile to work toward ].
More on……… Apress Practical REST on Rails 2