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

Re: multiplexing -- don't do it

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Tue, 03 Apr 2012 01:57:37 +1200
Message-ID: <4F79B051.4080801@treenet.co.nz>
To: ietf-http-wg@w3.org
On 1/04/2012 5:17 a.m., Adam Barth wrote:
> On Sat, Mar 31, 2012 at 4:54 AM, Mark Nottingham wrote:
>> On 31/03/2012, at 1:11 PM, Mike Belshe wrote:
>>> For the record - nobody wants to avoid using port 80 for new protocols.  I'd love to!  There is no religious reason that we don't - its just that we know, for a fact, that we can't do it without subjecting a non-trivial number of users to hangs, data corruption, and other errors.  You might think its ok for someone else's browser to throw reliability out the window, but nobody at Microsoft, Google, or Mozilla has been willing to do thatů
>> Mike -
>> I don't disagree on any specific point (as I think you know), but I would observe that the errors you're talking about can themselves be viewed as transient. I.e., just because they occur in experiments now, doesn't necessarily mean that they won't be fixed in the infrastructure in the future -- especially if they generate a lot of support calls, because they break a lot MORE things than they do now.
>> Yes, there will be a period of pain, but I just wanted to highlight one of the potential differences between deploying a standard and a single-vendor effort.  It's true that we can't go too far here; if we specify a protocol that breaks horribly 50% of the time, it won't get traction. However, if we have a good base population and perhaps a good fallback story, we *can* change things.
> That's not our experience as browser vendors.  If browsers offer an
> HTTP/2.0 that has a bad user experience for 10% of users, then major
> sites (e.g., Twitter) won't adopt it.  They don't want to punish their
> users any more than we do.
> Worse, if they do adopt the new protocol, users who have trouble will
> try another browser (e.g., one that doesn't support HTTP/2.0 such as
> IE 9), observe that it works, and blame the first browser for being
> buggy.  The net result is that we lose a user and no pressure is
> exerted on the intermediaries who are causing the problem in the first
> place.
> These are powerful market force that can't really be ignored.

So the takeway there is pay attention to the intermediary people when 
they say something cant be implemented (or won't scale reasonably).
With plenty of bias, I agree.

Received on Monday, 2 April 2012 13:58:04 UTC

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