Re: CoAP and new methods?

Well, they've got a separate registry for methods, so I'm not too concerned.

I'd be a little happier if they didn't seem to justify everything they did in terms of HTTP.

Cheers,


> On 9 May 2016, at 5:00 PM, Martin Thomson <martin.thomson@gmail.com> wrote:
> 
> I see that the core working group has adopted this work:
> 
> https://tools.ietf.org/html/draft-ietf-core-etch-00
> 
> This defines new methods for CoAP, which is (was?) very much *like* HTTP.
> 
> The new methods are:
> 
> FETCH, which looks like the proposed SEARCH in that it acts as a safe,
> idempotent retrieval.  It is different in that responses that are
> cacheable by default AND the request body forms part of the cache key.
> (I think that I got that right.)
> 
> iPATCH, which is like PATCH, but idempotent.
> 

--
Mark Nottingham   https://www.mnot.net/

Received on Monday, 9 May 2016 07:08:36 UTC