Difference between revisions of "Representational state transfer"

From Wiki @ Karl Jones dot com
Jump to: navigation, search
Line 16: Line 16:
  
 
* [[Architectural pattern]]
 
* [[Architectural pattern]]
 +
* [[Backbone.js]]
 
* [[HTML]]
 
* [[HTML]]
 
* [[Hypermedia]]
 
* [[Hypermedia]]
Line 30: Line 31:
 
* [https://en.wikipedia.org/wiki/Representational_state_transfer Representational state transfer] @ Wikipedia
 
* [https://en.wikipedia.org/wiki/Representational_state_transfer Representational state transfer] @ Wikipedia
 
* [https://en.wikipedia.org/wiki/Overview_of_RESTful_API_Description_Languages Overview of RESTful API Description Languages] @ Wikipedia
 
* [https://en.wikipedia.org/wiki/Overview_of_RESTful_API_Description_Languages Overview of RESTful API Description Languages] @ Wikipedia
 +
 +
[[Category:Computer science]]
 +
[[Category:Web design and development]]

Revision as of 03:48, 5 April 2016

Representational State Transfer (REST) is a software architecture style consisting of guidelines and best practices for creating scalable web services.

Description

REST is a coordinated set of constraints applied to the design of components in a distributed hypermedia system that can lead to a more performant and maintainable software architecture.

World Wide Web

The World Wide Web represents the largest implementation of a system conforming to the REST architectural style.

REST has gained widespread acceptance across the Web as a simpler alternative to SOAP and WSDL-based web services.

RESTful systems typically, but not always, communicate over the Hypertext Transfer Protocol with the same HTTP verbs (GET, POST, PUT, DELETE, etc.) used by web browsers to retrieve web pages and send data to remote servers.

See also

External links