In REST, compression, like encryption, is something that happens to a representation in transit, and must be undone before the client can use the representation.
Statelessness means that every HTTP request happens in complete isolation. When the client makes an HTTP request, it includes all information necessary for the server to fulfill that request. The server never relies on information from previous requests.
Generally, resources can have multiple presentations, mostly because there may be multiple different clients expecting different representations. Asking for a suitable presentation by a client, is referred as content negotiation. Server-driven Vs Agent-driven Content Negotiation If the selection of the best representation for a response is made by an algorithm located at the server, it […]
In the context of REST APIs, when making multiple identical requests has the same effect as making a single request – then that REST API is called idempotent. When you design REST APIs, you must realize that API consumers can make mistakes. They can write client code in such a way that there can be […]