REST also falls within the scope of Web Services technology. REST defines a set of architectural framework principles according to which system resource-centric Web services are designed, including how clients written in different languages can handle and transfer resource state over HTTP. REST is arguably the most dominant Web service design model in recent years, basically replacing SOAP and WSDL.
RPD vs. REST
Remote Procedure Call. RPC style development focuses on method calls between server/client and not on which protocol based on which network layer.
RPC style is represented by: XML-RPC, Big Web Services
XML-RPC is an RPC-style implementation that uses invocation of methods encapsulated in XML format and uses the HTTP protocol as the delivery mechanism.
The request method for XML-RPC is: the POST method of the HTTP protocol, and the data format of both the request and the response is XML.
The external interface to TestLink, the test case management system, is XML-RPC developed in PHP.
Big Web Services
That is, Big Web Services, is based on SOAP + WSDL + UDDI and other technologies to achieve the collective name of RPC style large Web services.
Representational State Transfer, i.e., representational layer state transformation.
REST is cross-language and cross-platform, and it is a Web Services that follows the REST style.
If an architecture conforms to REST principles, call it a RESTful architecture.
The presentation layer actually refers to the "resource", which is an entity of the network, or a specific piece of information. A URI (Uniform Resource Locator) can be used to point to it, and to get to this resource, you just need to access its URI.
Presentation layer (Representation)
A "resource" is an information entity that can have a variety of external manifestations, and the form in which the "resource" is concretely presented is called its "presentation layer".
eg: text can be represented in either txt format, or in HTML format, XML format, JSON format, or binary format.
The URI only represents the entity of the resource, not its form.
The HTTP protocol is a stateless protocol, all state is stored on the server side, if the client wants to operate the server, it has to make the server side "state transformation" by some means, and this transformation is built on top of the presentation layer, so it is "presentation layer state transformation".
The means used by the client can only be the HTTP protocol, specifically, inside the HTTP protocol, the four verbs that indicate the mode of operation: GET, POST, PUT and DELETE.
GET: used to obtain resources.
POST: used to create new resources (can also be used to update resources)
PUT: used to update resources
DELETE: used to delete resources
Taken together, the RESTful architecture can be summarized as follows.
Each URI represents a resource
between the client and the server, passing some sort of presentation layer of this resource
The client operates on the server-side resources through four HTTP verbs to achieve "presentation layer state transformation"
An encompassing relationship of these concepts above.
>>1、FDA Some varieties in the 100 top classical recipes catalogue cannot be developed2、Sailors Recommendation No 163、Samsung S9 vs Huawei Mate10ProiPX Who is the real flagship4、Is the market now a waitandsee or a phased entry5、Baidu App crowns Everyday and actually brings a lion to the set