IETF Logo Mail Archive

Re: How to express no matching results in HTTP SEARH method?

Henry Story <henry.story@gmail.com> Thu, 05 November 2020 03:21 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 465963A166C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 4 Nov 2020 19:21:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.748
X-Spam-Level:
X-Spam-Status: No, score=-2.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95FbXrsz2fsC for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 4 Nov 2020 19:21:08 -0800 (PST)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F080D3A166B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 4 Nov 2020 19:21:07 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1kaVpP-00087H-UI for ietf-http-wg-dist@listhub.w3.org; Thu, 05 Nov 2020 03:20:48 +0000
Resent-Date: Thu, 05 Nov 2020 03:20:47 +0000
Resent-Message-Id: <E1kaVpP-00087H-UI@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <henry.story@gmail.com>) id 1kaVpO-00086Q-Jb for ietf-http-wg@listhub.w3.org; Thu, 05 Nov 2020 03:20:46 +0000
Received: from mail-ej1-x629.google.com ([2a00:1450:4864:20::629]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <henry.story@gmail.com>) id 1kaVpN-0003NH-7t for ietf-http-wg@w3.org; Thu, 05 Nov 2020 03:20:46 +0000
Received: by mail-ej1-x629.google.com with SMTP id 7so519680ejm.0 for <ietf-http-wg@w3.org>; Wed, 04 Nov 2020 19:20:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QcTB/Fso9ay83bKA5AADn2Uqz7VHJBoLwYKJLyr/jhI=; b=pd3GgYciwZ0Sj8PkfBsm3fa5JVISu59NY6BN4TswDCZa9Q2pke4eQq2SHdYvJoSIm3 NSzBv+KoVyG6CRsgofhTXFHREVIFvcIbSOTe34igSXA6JrlEoyc11J1lGC7Sq0EIWMAW WAENM7wHCFL+nnEFfpe1gwtkc+3IJ3o24vE8CBugWbdXwdxHOrqWd+lgPzgt490igdoe 8t8e8KgWr2hYIRDo7IuQJFZP86hcrk8a7XsSdLk0hNtDiUtSRO/kNrDcuRwmxRKgfKOV lZKZa95ZMaLb/+UJR11cT3tpSKKrxR8r1BJ2a+65/yBzZJBVAsokzVu0kaHn9krI/BQB bj2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QcTB/Fso9ay83bKA5AADn2Uqz7VHJBoLwYKJLyr/jhI=; b=MqTM2PNh5zy52ieQbHZ4MJsdwJ18EqRYbeA0TZNyqQU0DRJzkWDBUNjVVj8CdW6Eh0 EH1Hi3cmkFFWa/E/kXCgysdE0E3lUtfJ66g61jUz3XoA7/g42Nq8w+rEdBajs2ReVGjE t+VimgTilWYU1kCeEHDfIAQgX90UbtbCcNhW8AnpKvKym++5msaa67e0GXaJIqUAke46 FBJF06XJzSwzaWStr6oeNelLmnPEUtc/IZYk4L5VApYCK0jWsbX9md14ufOLM4cW0vW+ MKISnfebGkrpRQ6vtvRQzJBs8hN/hnHxMsc2HdWiUitd9CI+GEs11/H5I31dapyvZFy9 OPoQ==
X-Gm-Message-State: AOAM533P+3T3miKowQziIWL4U1rFV99Uydso/YcZMkqIuEfvMy2QKpAU dhHwEkIZhoZsQKp/sHMbHwJ/Wkfhb0c=
X-Google-Smtp-Source: ABdhPJxWdueq+SaEpvV7594b/QXa4lbsuz5BmCGPaNnHylbPGSK1C2efCz+rZGZ0/UHlkygria9DvQ==
X-Received: by 2002:a17:906:f247:: with SMTP id gy7mr349191ejb.48.1604546433528; Wed, 04 Nov 2020 19:20:33 -0800 (PST)
Received: from ?IPv6:2003:cf:1708:a800:24ee:585f:13d6:8d30? (p200300cf1708a80024ee585f13d68d30.dip0.t-ipconnect.de. [2003:cf:1708:a800:24ee:585f:13d6:8d30]) by smtp.gmail.com with ESMTPSA id e18sm126693eja.124.2020.11.04.19.20.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Nov 2020 19:20:32 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Henry Story <henry.story@gmail.com>
In-Reply-To: <64090.1604498182@critter.freebsd.dk>
Date: Thu, 05 Nov 2020 04:20:31 +0100
Cc: Julian Reschke <julian.reschke@gmx.de>, ietf-http-wg@w3.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F431EB1-0216-40E1-AFC0-362986462AD3@gmail.com>
References: <CALOnmf-e24a=9ScKg3M==cSpG8TMd1JnMiecWgUMtD0a17xRgA@mail.gmail.com> <a599a2ba-ad97-b87d-6762-422cde1c1a41@gmx.de> <63989.1604496297@critter.freebsd.dk> <9a4f77e0-edc1-1813-a492-a19cd18410a2@gmx.de> <64090.1604498182@critter.freebsd.dk>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Received-SPF: pass client-ip=2a00:1450:4864:20::629; envelope-from=henry.story@gmail.com; helo=mail-ej1-x629.google.com
X-W3C-Hub-Spam-Status: No, score=-5.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1kaVpN-0003NH-7t dfe42b62e342c05478821192bf17ac85
X-Original-To: ietf-http-wg@w3.org
Subject: Re: How to express no matching results in HTTP SEARH method?
Archived-At: <https://www.w3.org/mid/6F431EB1-0216-40E1-AFC0-362986462AD3@gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/38168
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>


> On 4 Nov 2020, at 14:56, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
> 
> --------
> Julian Reschke writes:
>> Am 04.11.2020 um 14:24 schrieb Poul-Henning Kamp:
> 
>>> It might be a good idea to hash out a couple of general mechanisms
>>> in the spec, to provide mechanisms for traffic/load-engineering,
>>> at the very least something like "Dont-repeat-this-SEARCH: <seconds>" ?
>> 
>> That's all very interesting, but why is this relevant now, but not for
>> existing uses of POST we want to replace?
> 
> Because this is the century of the fruitbat, and we're trying to do a better
> job than back in the dark ages where things were just slapped together ?
> 
> Because SEARCH has much narrower and therefore more manageable semantics
> than POST, which can literally be and do anything ?

Structurally I think the following is true:

- POST creates a new resource - so it can have consequences like filling 
    a shopping cart or enrolling in the army
- GET fetches a representation without the client being bound by anything more
   than having seen the result. 

SEARCH (when restricted to one resource) is just a more  efficient GET,
just like PATCH is a more efficient PUT.

Henry

> 
> -- 
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe    
> Never attribute to malice what can adequately be explained by incompetence.
>

v2.23.0 | Report a Bug | By Email