mrsjae.blogg.se - Reason 6 tutorial

Reason 6 tutorial how to#

Hypermedia as the engine of application state – The client should have only the initial URI of the application.It should also provide information of the additional actions that the client can perform on the resource.

Reason 6 tutorial how to#

Self-descriptive messages – Each resource representation should carry enough information to describe how to process the message.

API consumers should use these representations to modify the resources state in the server.

Manipulation of resources through representations – The resources should have uniform representations in the server response.

Identification of resources – The interface must uniquely identify each resource involved in the interaction between the client and the server.The following four constraints can achieve a uniform REST interface: Multiple architectural constraints help in obtaining a uniform interface and guiding the behavior of components. Uniform Interfaceīy applying the principle of generality to the components interface, we can simplify the overall system architecture and improve the visibility of interactions. The six guiding principles or constraints of the RESTful architecture are: 1.1. These principles must be satisfied if a service interface needs to be referred to as RESTful.Ī Web API (or Web Service) conforming to the REST architectural style is a REST API. Like other architectural styles, REST has its guiding principles and constraints. Roy Fielding first presented it in 2000 in his famous dissertation. REST is an acronym for REpresentational State Transfer and an architectural style for distributed hypermedia systems.