IETF Logo Mail Archive

Re: Byte range PATCH

Eric J Bowman <mellowmutt@zoho.com> Tue, 09 August 2022 02:57 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 62AA4C159497 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 8 Aug 2022 19:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.759
X-Spam-Level:
X-Spam-Status: No, score=-2.759 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=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); domainkeys=pass (768-bit key) header.from=mellowmutt@zoho.com header.d=zoho.com; dkim=pass (1024-bit key) header.d=zoho.com
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 k982__kCtTyu for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 8 Aug 2022 19:57:29 -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 DFB4CC159827 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 8 Aug 2022 19:57:29 -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 1oLFNy-00FKSO-1G for ietf-http-wg-dist@listhub.w3.org; Tue, 09 Aug 2022 02:54:26 +0000
Resent-Date: Tue, 09 Aug 2022 02:54:26 +0000
Resent-Message-Id: <E1oLFNy-00FKSO-1G@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 <mellowmutt@zoho.com>) id 1oLFNx-00FKRR-1h for ietf-http-wg@listhub.w3.org; Tue, 09 Aug 2022 02:54:25 +0000
Received: from sender4-pp-o90.zoho.com ([136.143.188.90]) by titan.w3.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mellowmutt@zoho.com>) id 1oLFNv-00CrrJ-EB for ietf-http-wg@w3.org; Tue, 09 Aug 2022 02:54:24 +0000
ARC-Seal: i=1; a=rsa-sha256; t=1660013647; cv=none; d=zohomail.com; s=zohoarc; b=PQTGDIOJEtFW/xR7iUj7lO1RdS6j7kUnNU0EeNm5W0zMZTSAxYiT1+vJ+ijj/T5rZeBG5NJ5s9NNZYN+dXIhr1MvVTW/F8EHNRnVaXj34ZNL8UGGGqSaVCQMN+jX/J6cfPhCg1Ie4Q1ZuRlpqpqlS48Ah6yA6x9OU4n4G+EXMoE=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1660013647; h=Content-Type:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=vb4tYKTwbk5aQf0ssqn2pB5oMltLE/kWr1nKJBrQiTM=; b=LVuKeyzxRwFVZZ05tM0kkIqL8CJHsn7k3GJquDiK+he4278DdUOzYjUTJUB6APWRdNgjiPQ8Ypsu/vluHTm2BUcNKll8NP6C9GSBky1B8l3rMRTzvphXrYGR9Z0dAnvouflpFIDeYHd8Pzxq3+M9A+GgaPxQlK0Wym3XSULMHaw=
ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=zoho.com; spf=pass smtp.mailfrom=mellowmutt@zoho.com; dmarc=pass header.from=<mellowmutt@zoho.com>
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=date:from:to:cc:message-id:in-reply-to:references:subject:mime-version:content-type:user-agent; b=Ym4mHag9OUIqgDnUdQfjGpI8H9b/b+vxb1ZG3Lc8gaJZY4KQPEycXRnO3/jvYY/DFrMdICM4j0xm v+Q7Wfb8JaRHUEvYeFN5yZSNggUTFQXTw3OTWZjxQc8qGXVsntsK
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1660013647; s=zm2022; d=zoho.com; i=mellowmutt@zoho.com; h=Date:Date:From:From:To:To:Cc:Cc:Message-Id:Message-Id:In-Reply-To:References:Subject:Subject:MIME-Version:Content-Type:Feedback-ID:Reply-To; bh=vb4tYKTwbk5aQf0ssqn2pB5oMltLE/kWr1nKJBrQiTM=; b=aKZvTSzVibyLdg/sgoXIYBJgWQC6KYXMX1EeeZykKrtF5mz+2v/s47Eul+8y486A Hm6Kj4tfJvL1EkdTTGr+u2A0MczV6hPq2ROLhHAPbw/FM0Xj5oPVa7REkWbAkJ49H0A OyBZ/iaq3Fo3siieF7GDXbGTRcrvwRY94hShcsfo=
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1660013646792134.8422802470808; Mon, 8 Aug 2022 19:54:06 -0700 (PDT)
Received: from [65.117.211.248] by mail.zoho.com with HTTP;Mon, 8 Aug 2022 19:54:06 -0700 (PDT)
Date: Mon, 08 Aug 2022 19:54:06 -0700
From: Eric J Bowman <mellowmutt@zoho.com>
To: Roberto Polli <robipolli@gmail.com>
Cc: Austin William Wright <aaa@bzfx.net>, ietf-http-wg <ietf-http-wg@w3.org>
Message-Id: <1828086138e.d0af5fbd69268.3210279692370972800@zoho.com>
In-Reply-To: <CAP9qbHWtNL+U1XBHi5566S54wV2iazk2TnwZSKA5NtRVswkd=w@mail.gmail.com>
References: <E511F4BD-B422-46DA-8409-EBBD684098A6@bzfx.net> <CAP9qbHWtNL+U1XBHi5566S54wV2iazk2TnwZSKA5NtRVswkd=w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_171674_1232275535.1660013646735"
Importance: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Feedback-ID: rr080112273ddb4c582b7399112a1c3d5c0000cda1acb8876e9b945ee910b9e7cdc9a3f53988e8f811bea479:zu080112276e3bcf9e36e9a2a7483a582900007511076a69302b591dd9416a189929e1c38b3ff724795f0095:rf080112317b7286933414db79e701e8720000f5c0a11ca7c6dcbd0cde4f13591b8e5f8cbc6942bf52e341313bdba1ac68954efbb521:ZohoMail
Received-SPF: pass client-ip=136.143.188.90; envelope-from=mellowmutt@zoho.com; helo=sender4-pp-o90.zoho.com
X-W3C-Hub-DKIM-Status: validation passed: (address=mellowmutt@zoho.com domain=zoho.com), signature is good
X-W3C-Hub-DKIM-Status: validation passed: (address=mellowmutt@zoho.com domain=mellowmutt@zoho.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-4.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, 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_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1oLFNv-00CrrJ-EB 18647b3327df63f9972cc8d5517da00d
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Byte range PATCH
Archived-At: <https://www.w3.org/mid/1828086138e.d0af5fbd69268.3210279692370972800@zoho.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40314
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>

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.
 
 >
> 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.



-Eric

v2.23.0 | Report a Bug | By Email