Page History

...

The SRP HTTP Framework does not enforce statelessness , but it also does not nor does it offer any tools to make the system stateful. Much of this is how the API developer implements the response to a particular requestStatelessness is really a matter of self-governance in the design of the API. Developers can move toward statelessness by avoiding, or minimizing database locks, and returning the resource with meta-data metadata (see Uniform Interface below) that instructs the client how it can request a state change. Stateless APIs are not difficult to implement unless they need to operate within the same application that requires a stateful design, such as one that also supports a traditional OpenInsight desktop environment. In these cases, clients typically maintain pessimistic locks on database rows, which could create conflicts in the way a web API interacts with the same row.

Uniform Interface

REST, as it is argued, attempts to use HTTP more faithfully. This is the primary basis for a uniform interface. That is, by adhering to the published HTTP standards, API producers and consumers can better anticipate how to interface with each other. It also provides for greater decoupling, allowing independent evolution between the client and the server.

...