W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

Re: Support for compression in XHR?

From: Stewart Brodie <stewart.brodie@antplc.com>
Date: Tue, 9 Sep 2008 14:08:45 -0400
To: Dominique Hazael-Massieux <dom@w3.org>
Cc: public-webapps@w3.org
Message-ID: <gemini.k6xx2l000eawg03q4.stewart.brodie@antplc.com>

Dominique Hazael-Massieux <dom@w3.org> wrote:

> 
> Le mardi 09 septembre 2008 à 09:02 -0400, Boris Zbarsky a écrit :
> > HTTP has Content-Encoding and Transfer-Encoding, no?  No special effort 
> > on the part of XMLHttpRequest is needed to make use of those, as long as

> > the underlying HTTP implementation supports them.
> 
> Well, at least when an outgoing XmlHttpRequest goes with a body, the
> spec could require that upon setting the Content-Encoding header to
> "gzip" or "deflate", that the body be adequately transformed. Or is
> there another e.g. to POST a gzip request with Content-Encoding?

I disagree with any proposal that allows the application layer to forcibly
interfere with the transports layer's internal workings.  Use of encodings,
persistent connections, on-the-fly compression are entirely internal to the
transport mechanism.

If you want to allow hints that the UA can ignore, that's fine - but
"require" is silly - it might make the data larger, for all you know. Leave
it as a QoI issue for the user agent to sort this out for itself.

-- 
Stewart Brodie
Received on Tuesday, 9 September 2008 19:57:02 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:27 GMT