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

Re: multiplexing -- don't do it

From: Willy Tarreau <w@1wt.eu>
Date: Sat, 31 Mar 2012 09:30:04 +0200
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Mike Belshe <mike@belshe.com>, "Adrien W. de Croy" <adrien@qbik.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Roberto Peon <grmocg@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <20120331073004.GN14039@1wt.eu>
Hi Julian,

On Sat, Mar 31, 2012 at 08:57:03AM +0200, Julian Reschke wrote:
> On 2012-03-31 01:53, Mike Belshe wrote:
> >...
> >Before thinking this way we should look at how well other mandatory but
> >optional to use features have turned out.
> >
> >One such example is pipelining.  Mandatory for a decade, but optional to
> >implement. We still can't turn it on.
> >...
> But then many people have it turned on, and it seems to be on by default 
> in Safari mobile. Maybe the situation is much better than you think.
> >...
> >Options simply don't work - we need to make this stuff mandatory from
> >the get-go or it  is very likely to have the same result that we've seen
> >in the past.
> >...
> I don't think that's correct.
> Options do not work if and only if they are usually not switched on.
> For instance, if header compression is optional, but common UAs will use 
> it by default, it *will* be implemented.

Mike suggested that mandatory features must not necessarily be used but at
least be implemented. And in fact, whatever concerns the connection setup
from the client to the server has to be implemented ; if a browser sends
compressed headers to a gateway that cannot decompress them, it will fail
(which was my reason to try something cheaper than zlib from the server's
point of view). Not supporting the other direction is not an issue however
since the server knows what the client supports.

Best regards,
Received on Saturday, 31 March 2012 07:30:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:01 UTC