- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 6 Aug 2015 09:05:08 +1000
- To: Phil Hunt <phil.hunt@oracle.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
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. Did you consider using a different request media type? Regards, > On 21 Jul 2015, at 10:42 pm, Phil Hunt <phil.hunt@oracle.com> wrote: > > Link as requested by @mnot for the SCIM thought experiment on the user of the HTTP Search draft. > > https://tools.ietf.org/html/draft-hunt-scim-search-00 > > Phil > > @independentid > www.independentid.com > phil.hunt@oracle.com > -- Mark Nottingham https://www.mnot.net/
Received on Wednesday, 5 August 2015 23:05:37 UTC