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: Thu, 11 Sep 2008 13:04:36 -0400
To: Jonas Sicking <jonas@sicking.cc>
Cc: Dominique Hazael-Massieux <dom@w3.org>, public-webapps@w3.org
Message-ID: <gemini.k71jfo000t5bl0240.stewart.brodie@antplc.com>

Jonas Sicking <jonas@sicking.cc> wrote:

> Stewart Brodie wrote:

> > 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.
> 
> This is fine for transport mechanism where capability negotiation is 
> two-way.
> 
> However a relatively common use case for the web is transferring things 
> through HTTP, where the HTTP client has no way of getting capability 
> information about the HTTP server until the full request has already 
> been made.

I don't believe that this is the case.  Even in the case where you are using
a cross-domain request to a server that the client has not talked to before,
the client always has the option of attempting an OPTIONS request to see
what the server offers.  It might choose to do that if it's going to have to
send a large entity-body in the request; it might not bother if the entity
is small.

The application cannot possibly know that the request isn't going to get
routed through some sort of transparent proxy - or normal proxy for that
matter - where your forcing of encoding will fail.  That is why it is a
transport-level option, not an application-level option.


-- 
Stewart Brodie
Received on Thursday, 11 September 2008 17:05:29 GMT

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