GET FRESH BODY SKIN
Besides the actual resource holding more or less the data of the business object, you also have a form-resource that teaches clients on how a request has to look like and potentially a resource that stores all of the request parameters for laster usage.Looking for a bar that leaves skin feeling refreshed, hydrated, and invigorated? Dove Men+Care Extra Fresh Body and Face Bar delivers a deep, refreshing clean and hydration. This also goes hand in hand by Fielding's statement that a REST architecture usually has plenty more resources than domain objects. On doing this, any response yielded by that query is yet again cacheable and thus in-line with any constraints put up by the REST architecture. A client could now simply issue a GET request against this pre-stored query in order to retrieve its result. This resource in essence would encapsulate all of the requests parameters such as query term or fields. The product resource of such a form-resource could be stored further and given a meaningful name intended for later usage as well, i.e. This way clients will also learn on the fly about the new or updated properties a certain resource supports and expects and thus wont need any external documentation.
In case of a modification an unsafe operation is performed on that form-resource that leads to invalidation of any stored representation for the respective URI. The advantage on introducing an intermediary layer that describes what properties a resource supports is that this representation is in essence cacheable as it probably wont change often. Though most of those so called REST APIs (which truely behave like classic RPC ones) do not even consider form-like representations at all although some drafts exists such as hal-forms, halo+forms or ion. But these forms also teach a client on where to send the request to, which HTTP operation to use and, mostly implicitly given, also the media type to use to marshal the data into before sending the actual request.
In HTML we are all to familiar with Web forms and how they can be used to teach clients on what properties a resource supports. Please, regard this post as some kind of addendum to Voice's post as his post, IMO, is missing an important design philosophy often used in REST architectures: servers should teach clients what they need to take next actions! The latter one, however, should always be treated with care as once you let external peers into this environment they need customization as well. each client, server and intermediary is run by you)
GET FRESH BODY FULL
use customized methods when you in full control of the environment (i.e.use POST if other methods are not sufficient enough.Voice already mentioned most of the stuff relevant to REST, such as GET /c30e910e-7baa-4c31-9481-4c84c12884a1Ĭontent-Location: /c30e910e-7baa-4c31-9481-4c84c12884a1įollowing the standards, you can combine those two ideas to save a round trip POST /fooįrom there, it's a small step to POST /foo So we POST some information, and that information gets associated with a new URI controlled by the server, and then subsequent attempts to GET the resource give you the results you want. one way to achieve what you want without "breaking the rules" is to think about creating a new resource that is the results of your query. REST says "use the appropriate method defined in the uniform interface" HTTP says "use POST when no more specific method fits".īut if you are in an environment that won't accept that. REST doesn't define any sort of "create" constraint.
It's not REST because POST should be used to create data
POST serves many useful purposes in HTTP, including the general purpose of “this action isn’t worth standardizing.” That said, if you are trying to color inside the lines, it is okay to use POST. And if that is the case, you might as well define your own HTTP method with the semantics that you want it to have.įor example, you might look into HTTP SEARCH, and see if those semantics are a better fit for what you are trying to do. In effect, GET with a body is only going to work if you control the client, the web server, and the components in between. For instance, caches will be using the target-uri as the primary cache key, and won't be considering the body at all. You can't count on general purpose components doing useful things with the body. I think the better solutions will be to use HTTP Get with bodyĪ payload within a GET request message has no defined semantics sending a payload body on a GET request might cause some existing implementations to reject the request.
0 kommentar(er)
