Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COI surprised that you would not see this as just another "creative" way to use HTTP. I'm assuming you don't have a problem with case 1. For case 2 if you assume that the resource is a "data processing" resource, then I don't see a problem with doing POST that returns 303. Is the problem that the client is using the same resource for both scenarios?
      singulars
    2. COPUT is meant to be used when you know the URI of the resource. In this case, the client does not know the final URI of the resource. (Did you miss my mention that the client doesn't know the key, e.g. 456, in advance? The server decides the key.) POST also doesn't require state changes on the server. It means there *might* be state changes on the server. I'll try to dig up places where I've read this. Regardless, I appreciate your comments, but this is also a case to me where the simplicity of POST here by far outweighs the possible slightly better semantics of PUT + If-None-Match.
      singulars
    3. COHere's an article that confirms my point: http://jcalcote.wordpress.com/2008/10/16/put-or-post-the-rest-of-the-story/ "Create = POST if you are sending a command to the server to create a subordinate of the specified resource, using some server-side algorithm." / "Create can be implemented using an HTTP PUT, if (and only if) the payload of the request contains the full content of the exactly specified URL." / "POST operations may or may not result in additional directly accessible resources."
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload