W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2022

Re: Draft v1 Update for Resumable Uploads

From: Eric J Bowman <mellowmutt@zoho.com>
Date: Mon, 20 Jun 2022 01:56:38 -0700
To: "Eric J Bowman" <mellowmutt@zoho.com>
Cc: "Julian Reschke" <julian.reschke@gmx.de>, "ietf-http-wg" <ietf-http-wg@w3.org>
Message-Id: <18180540509.127d3d33c42735.7582968511965974029@zoho.com>

> Bound to be fresh if it's resident on the origin server, no? 

> Come to think of it, the entity body could list additional target 

> URIs... apply googly-eye filter to all kitty pics. Haha, lolz, now 

> revert on all non-Hitler kitties.


I'm not suggesting to change RFC 5789 regarding atomicity of the transaction. However, this is the first use-case I've come up with for server push. I want a 204 back for each file, or directory, listed in my PATCH entity-body. Then I can re-send individual requests for any missing links, after an appropriate timeout.

Note that while my example takes 2-3 round trips to implement, the result can be pretty much an infinite number of files PATCHed. Maybe PATCH _can_ be anarchically scalable? When needed.

Received on Monday, 20 June 2022 08:56:56 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:44:07 UTC