Re: Call for Adoption: SEARCH method

• From: Philippe Mougin <pmougin@acm.org>
• Date: Fri, 27 Nov 2020 17:41:47 +0100
• To: Julian Reschke <julian.reschke@gmx.de>
• Cc: Asbjørn Ulsberg <asbjorn@ulsberg.no>, James Fuller <jim@webcomposite.com>, Greg Wilkins <gregw@webtide.com>, HTTP Working Group <ietf-http-wg@w3.org>
• Message-Id: <00E88E9A-0D35-4D8C-A09F-6A463FFE7495@acm.org>

> Le 27 nov. 2020 à 14:32, Julian Reschke <julian.reschke@gmx.de> a écrit :
> 
> Am 27.11.2020 um 14:25 schrieb Asbjørn Ulsberg:
>> In my view, SEARCH as currently specified only solves the first of
>> five desirable properties of a new HTTP method:
>> 
>> 1. Explicit support for a request payload.
>> 2. Safe.
>> 3. Idempotent.
>> 4. Cacheable by default (keyed by payload).
>> 5. Content-Type agnostic.
> 
> Hmmm?? It solves 1...3, unless I'm missing something.

Looks indeed that it explicitly solves it. But only for the narrow use case of search operations, with no clear benefit from this limitation.

Best,

Philippe Mougin

Received on Friday, 27 November 2020 16:42:04 UTC