Representational State Transfer - Wikipedia, the free encyclopedia 

[ edit ] Principles REST's proponents argue that the Web enjoyed the scalability and growth that it has had as a direct result of a few key design principles: Application state and functionality are divided ... into resources Every resource is uniquely addressable using a universal syntax for use in hypermedia links All resources share a uniform interface for the transfer of state between client and resource, consisting of A constrained set of well-defined operations A constrained set of content types , optionally supporting code-on-demand A protocol that is: Client/Server Stateless Cacheable Layered REST's client-server separation of concerns simplifies component implementation, reduces the complexity of connector semantics, improves the effectiveness of performance tuning, and increases the scalability of pure server components. Layered system constraints allow intermediaries--proxies, gateways, and firewalls--to be introduced at various points in the communication without changing the i   [More...] [Less...]