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

Re: current HTTP/2 spec prevents gzip of response to "Range" request

From: Roland Zink <roland@zinks.de>
Date: Wed, 26 Mar 2014 12:23:18 +0100
Message-ID: <5332B8A6.6050905@zinks.de>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
CC: HTTP Working Group <ietf-http-wg@w3.org>
On 26.03.2014 12:01, Poul-Henning Kamp wrote:
> In message <5332AFD6.1000105@zinks.de>, Roland Zink writes:
>
>> Looks like there is the log file example mentioned in the discussion.
>> Where this is often used is in playing videos (although there often no
>> gzip is used but I have seen this too). Many players allow the user to
>> jump within the video.
> The logfile example I'm just going to ignore because it is bogus on
> so many planes that it's not even funny:  The exact same problem
> exists with compressed logfiles when no HTTP is involved at alle.
>
> Video formats defined exactly so that they are searchable, and if
> anybody wastes their time gzip'ing videos, they have bigger problems
> than not being able to search them.
I know people which are doing this exactly because video formats are 
searchable. Padding is used to make search work and gzip is used to get 
rid most of the padding on the wire.
Received on Wednesday, 26 March 2014 11:23:40 UTC

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