W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2007

Re: Suggestion for NEW Issue: Pipelining problems

From: Harald Tveit Alvestrand <harald@alvestrand.no>
Date: Thu, 19 Jul 2007 19:01:04 -0700
To: Jamie Lokier <jamie@shareable.org>, "Roy T. Fielding" <fielding@gbiv.com>
Cc: yngve@opera.com, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <9094D8ED937AA98DFD5868EE@B50854F0A9192E8EC6CDA126>



--On 18. juli 2007 11:06 +0100 Jamie Lokier <jamie@shareable.org> wrote:

> I suspect pipelining was added to HTTP because it's such a trivial and
> natural change - in fact no change to many servers - that it was
> thought it might be easy to deploy.  And there is no excuse really for
> getting it wrong, it really is quite trivial to implement.

actually pipelining (as far as I remember the debates - it is many years 
ago now) was added in an effort to get HTTP to be a better-behaved network 
citizen.

One interesting feature of one-TCP-connection-per-request is that TCP 
congestion control really doesn't kick in until about packet 6 or so, after 
the slow-start phase is over - and when most TCP connections are shorter 
than 6 packets, it means that a huge percentage of the Internet traffic 
really is travelling the Internet with no congestion at all - leaving the 
Internet unprotected from another round of congestion collapse.

It seems, however, that the Internet has survived the situation - once the 
majority of traffic is (congestion-controlled) filesharing, perhaps the 
not-so-nice HTTP sessions don't count for that much after all....

                   Harald
Received on Friday, 20 July 2007 12:27:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:15 GMT