Re: Byte range PATCH

Austin William Wright <aaa@bzfx.net> Tue, 09 August 2022 05:36 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 5A91EC14F613 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 8 Aug 2022 22:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.76
X-Spam-Level:
X-Spam-Status: No, score=-2.76 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.248, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bzfx.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXJfdWDrYHBa for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 8 Aug 2022 22:36:07 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36AD5C14F718 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 8 Aug 2022 22:36:06 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1oLHuF-00Fajz-HH for ietf-http-wg-dist@listhub.w3.org; Tue, 09 Aug 2022 05:35:55 +0000
Resent-Date: Tue, 09 Aug 2022 05:35:55 +0000
Resent-Message-Id: <E1oLHuF-00Fajz-HH@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <aaa@bzfx.net>) id 1oLHuD-00Faj1-SS for ietf-http-wg@listhub.w3.org; Tue, 09 Aug 2022 05:35:53 +0000
Received: from mail-pg1-x52e.google.com ([2607:f8b0:4864:20::52e]) by titan.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <aaa@bzfx.net>) id 1oLHuC-00CuVc-Gz for ietf-http-wg@w3.org; Tue, 09 Aug 2022 05:35:53 +0000
Received: by mail-pg1-x52e.google.com with SMTP id c24so5618045pgg.11 for <ietf-http-wg@w3.org>; Mon, 08 Aug 2022 22:35:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bzfx.net; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=zLK7Sa/Hy4FUCsVGdmulaDO816eGM8HyRyv83PgdX8k=; b=JtO2lBIt3aTZoyuUgdk9CVT/bVnGHWh7a+dB9XJjsgERw1aYyKeF20cM/MwisqnrOW JdI0J/NiRtFm+W7DU9KDK8dMMxI82cjiZ8KEb/+4P08rpcamlIlLQ5p4hyHf9pIo1PHO kvyGo2IUC2io73WVNsm2ssZ9XXCIQ01r4tfUY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=zLK7Sa/Hy4FUCsVGdmulaDO816eGM8HyRyv83PgdX8k=; b=z0VVp6+KYP7AePMv4DB6vZbtaBmt5APGCiH9UqyeoOhMIOlzT/vHCk1cP15MQ1HlF/ QZzSBSyxmE+Se/zCCS0+PUECfgxsHuSvYU5CwNtPIV3CnhhkTP5hvdzBKsBo5/j4TLea hxQsSy5tsEAxWE45PC6Lh5tcQACoIezDv8jT085BXGBtK7ETcCUpTcciN4X4lE5W2lV2 7kdb7dkhStMt+vv+TmtD3f4AooQkh9TT7K+ZtK8lSTL72Q7I29iPiZ9q6XWZjt0madqe dKNG4kNyamroQypJZTdp9bYCRoFhS4LKg2QSGxpdzI7EWa5eRiZ7yaV6q5omX6fKZRPm Aynw==
X-Gm-Message-State: ACgBeo0Z2RGaWzWlEv10qvLjYEdls/6lzpTKiZXJtBbPu3l9bNFc7rXh Z1x9slFjczao2Hj2STHCnDGZKw==
X-Google-Smtp-Source: AA6agR5HBN8gfMchfRuGrnbrsEgi0n7H4ZiMzHgHmjUee/bpAeKYLNE4s8XtSt6oggqjlR2Bv8WRvg==
X-Received: by 2002:a63:6bc5:0:b0:41c:26d2:81e2 with SMTP id g188-20020a636bc5000000b0041c26d281e2mr17964348pgc.522.1660023341377; Mon, 08 Aug 2022 22:35:41 -0700 (PDT)
Received: from smtpclient.apple (71-223-183-211.phnx.qwest.net. [71.223.183.211]) by smtp.gmail.com with ESMTPSA id p124-20020a622982000000b0052da33fe7d2sm9806640pfp.95.2022.08.08.22.35.39 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Aug 2022 22:35:40 -0700 (PDT)
From: Austin William Wright <aaa@bzfx.net>
Message-Id: <734BB380-2BA8-45C2-BECB-2C33129FB168@bzfx.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EE6FD3D4-C4CA-4C96-9B7C-55757F2E070C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Date: Mon, 08 Aug 2022 22:35:39 -0700
In-Reply-To: <1828086138e.d0af5fbd69268.3210279692370972800@zoho.com>
Cc: Roberto Polli <robipolli@gmail.com>, ietf-http-wg <ietf-http-wg@w3.org>
To: Eric J Bowman <mellowmutt@zoho.com>
References: <E511F4BD-B422-46DA-8409-EBBD684098A6@bzfx.net> <CAP9qbHWtNL+U1XBHi5566S54wV2iazk2TnwZSKA5NtRVswkd=w@mail.gmail.com> <1828086138e.d0af5fbd69268.3210279692370972800@zoho.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Received-SPF: pass client-ip=2607:f8b0:4864:20::52e; envelope-from=aaa@bzfx.net; helo=mail-pg1-x52e.google.com
X-W3C-Hub-DKIM-Status: validation passed: (address=aaa@bzfx.net domain=bzfx.net), signature is good
X-W3C-Hub-Spam-Status: No, score=-6.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1oLHuC-00CuVc-Gz c471987783beb053f539de57b43d0c4e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Byte range PATCH
Archived-At: <https://www.w3.org/mid/734BB380-2BA8-45C2-BECB-2C33129FB168@bzfx.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40316
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 Aug 8, 2022, at 19:54, Eric J Bowman <mellowmutt@zoho.com> wrote:
> 
> Roberto Polli wrote ---
> 
> >
> > Content-Range might arise (e.g. you'd need to ensure that the server 
> > support content-range in requests to avoid replacing an existing 
> > resource with the "partial" representation conveyed in PUT). In 
> > general RFC9110 is now more flexible on PUT + partial representations 
> > than in the past.
> >
> 
> That's both an argument for, and against, deprecating PATCH. Just throwin' that out there because it's really only just occurred to me, and I'm surprisingly open to it.

PATCH is not causing anyone any trouble.

> 
> >
> > content-ranges in the same request and it is simpler to just issue 
> > multiple requests so that each can have its own representation 
> > metadata managed directly via HTTP. 
> >
> 
> +1
> 
> In lieu of a document titled "multiple HTTP requests considered harmful" maybe I should write one titled "overloading HTTP requests considered harmful?" It's become so de rigueur to eliminate protocol round-trips that we're now entertaining it even on uploads where it matters not.

This proposal does not "overload” anything. If anything, I’m writing this to avoid overloading PUT or POST with semantics that may be misunderstood by origin servers.

The PATCH semantics, by contrast, are being used exactly as intended and understood.

Thanks,

Austin.