REST-based Distributed-System Pattern

From GM-RKB
Jump to: navigation, search

A REST-based Distributed-System Pattern is a stateless client-server Distributed-System Pattern with Cacheable systems, Layered systems, and Uniform Interfaces



References

2013

  • (Wikipedia, 2013) ⇒ http://en.wikipedia.org/wiki/representational_state_transfer Retrieved:2013-12-16.
    • Representational State Transfer (REST) is an architectural style consisting of a coordinated set of constraints applied to components, connectors, and data elements, within a distributed hypermedia system. REST ignores the details of component implementation and protocol syntax in order to focus on the roles of components, the constraints upon their interaction with other components, and their interpretation of significant data elements.[1] The term representational state transfer was introduced and defined in 2000 by Roy Fielding in his doctoral dissertation at UC Irvine.[1] REST has been applied to describe desired web architecture, to identify existing problems, to compare alternative solutions, and to ensure that protocol extensions would not violate the core constraints that make the Web successful. Fielding used REST to design HTTP 1.1 and Uniform Resource Identifiers (URI). [2] [3] The REST architectural style is also applied to the development of Web services, as an alternative to other distributed-computing specifications such as SOAP.
  1. 1.0 1.1 Chapter 5 of Fielding's dissertation is "Representational State Transfer (REST)".
  2. RFC 1945
  3. RFC 2616