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: Sun, 19 Jun 2022 03:40:39 -0700
To: "Guoye Zhang" <guoye_zhang@apple.com>
Cc: "gs-lists-ietf-http-wg" <gs-lists-ietf-http-wg@gluelogic.com>, "ietf-http-wg" <ietf-http-wg@w3.org>
Message-Id: <1817b8ce1c8.12200c57b32105.652822867537979220@zoho.com>

> Apple has a Feedback Assistant app which allows customers to

> file bug reports and upload device diagnostics. These diagnostics

> are usually hundreds of megabytes in size, and if interrupted, we

> have to upload them again from the beginning. This has been 

> one of the most common complains we receive.


FTP is your friend. Well, SFTP/FTPS anyway. If you can't tighten the screw with a hammer, maybe try a screwdriver.


> From my reading of the PATCH standard, media type should be the

> type of the content that we are trying to modify.


RFC 5789 states:

"The PATCH method requests that a set of changes described in the request entity be applied to the resource identified by the Request-URI. The set of changes is represented in a format called a 'patch document' identified by a media type."

Suggest brushing up on "media type". You're modifying a resource, not a type of content. A text/html representation of a CSV diagnostic file may be generated for rendering in a browser. Probably best to patch the resource by sending a snippet of CSV, as patching the HTML *representation* may inadvertently break the CSS. Not to mention needs reverse-transformed before applying to the resource.

You just need a "patch document" with a media type defining it as CSV, maybe even with line numbers.

Received on Sunday, 19 June 2022 10:41:07 UTC

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