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

Re: Range Requests vs Content Codings

From: Zhong Yu <zhong.j.yu@gmail.com>
Date: Sat, 21 Jun 2014 13:02:43 -0500
Message-ID: <CACuKZqFPUvo=O7PzNmgN6qTmSLuYmYeUNvTCsOU21FwJTin+ng@mail.gmail.com>
To: K.Morgan@iaea.org
Cc: Roland Zink <roland@zinks.de>, HTTP Working Group <ietf-http-wg@w3.org>, C.Brunhuber@iaea.org
On Sat, Jun 21, 2014 at 11:34 AM,  <K.Morgan@iaea.org> wrote:
> We have rapidly growing append-only files.  Currently we use gzip Transfer-Encoding to compress an identity range request.  But since T-E went away (again) in h2, it's no longer possible.

damn it... I just implemented the feature on my server. another fool's errand.


> I realize it's a controversial issue, but if I understand correctly, h2 is supposed to replace *everything* you could do in 1.1.
> As far as I can tell, there are four solutions for maintaining this capability...
> 1. Julian's bbcc
> 2. Matthew's DATA frame compression - possibly as an extension now that it was removed from the main spec.
> 3. My & Christoph's Message-Encoding HTTP extension (an end-to-end version of T-E that is applied after C-E, but before T-E)
> 4. Keep T-E in h2 (I dare say nobody wants this solution)
> [1] http://www.nationmultimedia.com/breakingnews/Google-to-pay-Firefox-almost-1-billion-dollars-in--30172517.html
> This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
Received on Saturday, 21 June 2014 18:03:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:31 UTC