- From: Michael Sweet <msweet@apple.com>
- Date: Wed, 05 Aug 2015 19:32:16 -0400
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Phil Hunt <phil.hunt@oracle.com>, HTTP Working Group <ietf-http-wg@w3.org>
> On Aug 5, 2015, at 7:05 PM, Mark Nottingham <mnot@mnot.net> wrote: > > Hi Phil, > > Reading that document: > > """ > In contrast, using HTTP POST has the disadvantage of overloading POST to perform another function other than creating new SCIM resources. > """ > > POST's semantics aren't "create a resource" — they're "process this data" with the possible side effect of creating a resource. > > POST can easily dispatch on request characteristics (e.g,. request body media type) to determine what the appropriate action is; there is no requirement that POST map to only one set of semantics per URL. This is exactly how IPP works - each POST request contains an IPP request message complete with operation code and attributes (parameters). Each response contains an IPP response message with an IPP status code and more attributes. Some operations create objects, others cancel/delete them, etc. _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair
Received on Wednesday, 5 August 2015 23:32:49 UTC