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

Re: Design Issue: GZIP flag on DATA Frames

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Tue, 21 May 2013 21:53:36 +0000
To: Bjoern Hoehrmann <derhoermi@gmx.net>
cc: James M Snell <jasnell@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <5447.1369173216@critter.freebsd.dk>
In message <8ipnp8hapu1949rd0mahtoasm60mm1i46v@hive.bjoern.hoehrmann.de>, Bjoer
n Hoehrmann writes:

>I understood Poul-Henning Kamp to
>be considering going one step further and offering no means to define
>new compression schemes.

Ok, so let me clarify:

I have always hated the confusion in HTTP/1 between content compressed
for transport purposes, and content compressed for application purposes.

In the former class you have HTML, javascript, CSS etc.

In the latter class you have things like .tgz, gzip'ed XML etc.

It's the former class I want to cut all the way into the bone
and take out of "Accept-Encoding" negotiation.

Accept-Encoding should be reserved only for the second class.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Tuesday, 21 May 2013 21:53:59 UTC

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