Comments on: Google Chrome: One thing we do know… (HTTP Pipelining)

By: Alex

Alex — Tue, 13 Jul 2010 23:08:41 +0000

“Pipelining only works when the remote server supports it, if the remote server fails to pipeline then your page will actually load much slower.”Why would this be? I've never seen it be “much slower”, nor can I think of any reason this would be the case.”This is the case with IIS 4 and 5 which are common enough to cause concern. Also it turns out that some mods to Apache don't pipeline properly, resulting in garbled output.”That's the real reason nobody uses it: at best, it's much faster, but at worst, it fails horribly.

By: roy554

roy554 — Wed, 17 Mar 2010 01:50:25 +0000

Great post, Thanks,You can test pipeline using this free HTTP pipeline tool and test the response return from the web when sending different HTTP Get or post with pipeline:http://soft-net.net/SendHTTPTool.aspx

By: Zauber Exonar

Zauber Exonar — Mon, 01 Mar 2010 09:09:28 +0000

IIS 4 and 5 not supporting pipelining is no reason for it to be pulled from the RFC. Bear in mind: IIS is microsoft technology. And microsoft has a history of ignoring, twisting, or abusing standards. Especially when it benefits them. See J++ for a good example of the twisting/abusing concept.

By: Stephen Pierzchala

Stephen Pierzchala — Wed, 01 Jul 2009 09:29:18 +0000

Cool. Now, if it's not supported by anyone, it should get pulled from the RFC. And now that the browser engines are almost all abstracted from the browser that wraps around them, maybe it's time to look at what works to make browsers and content delivery faster.

By: Mark Pauley

Mark Pauley — Wed, 01 Jul 2009 05:52:27 +0000

You're wrong. Chrome could pipeline, nothing in Webkit prevents this. Chrome doesn't use the CFNetwork loader nor does WebKit marry the browser to any given network / HTTP stack, just look at the code. The reason Chrome doesn't support pipelining is likely to be the same reason that no other browser pipelines out of the box: pipelining is broken. Pipelining only works when the remote server supports it, if the remote server fails to pipeline then your page will actually load much slower. This is the case with IIS 4 and 5 which are common enough to cause concern. Also it turns out that some mods to Apache don't pipeline properly, resulting in garbled output. The ultimate solution will be a compromise as is seen with the fledgling 'support' for pipelining in Firefox's HTTP stack which is off by default.

By: Stephen Pierzchala

Stephen Pierzchala — Wed, 01 Jul 2009 03:29:18 +0000

By: Mark Pauley

Mark Pauley — Tue, 30 Jun 2009 23:52:27 +0000