The full name of rest is representational state transfer, which is an architectural design style. State transfer is said to transfer the representation of resource state between client and server side
The main principles of rest include: The URL represents the resource, and the HTTP method represents the operation. Get/post/put/delete/increment/change/delete respectively
It is a kind of design way of resource-oriented service
It emphasizes resource-centric, and regulates the style of URIs
In rest, a resource can be understood as a URI, represented as a form of resource rendering, such as returning JSON or XML
-
main features:
-
stateless, communication must be stateless in nature, session state is guaranteed to be saved on client
-
cache, the client can cache the response data, and later the same request can be reused
-
layered system, by restricting the behavior of components, By decomposing the schema into layers of several tiers, the complexity of the entire system provides a boundary that improves the underlying independence
-
on-demand code to extend the functionality of the client by downloading and executing some code
This article is from the "ten-li Rice flower" blog, please be sure to keep this source http://5880861.blog.51cto.com/5870861/1809704
A little understanding of rest style