Chrome 17 Gets HTTP Pipelining

Google is a bit late to the party with this feature. Opera has had pipelining support since version 4 and Firefox has also included some customization freedom for users to adjust pipelining to alleviate the page load delays that are cause in high-latency situations.

It is unclear when pipelining will be available by default. However, Chrome 17 is about 12 - 14 weeks from its final release and there is plenty of time to prep the feature. You can test drive pipelining in Chrome by downloading a recent Chromium snapshot. The feature is integrated in the browser in build versions 106364 and higher.

Article continues below
TOPICS
Wolfgang Gruener
Contributor
  • Randomacts
    Chrome 18 does your homework!!!...

    Seriously tho.. I wish they would do.01 ect updates for most of these updates
    Reply
  • JOSHSKORN
    RandomactsSeriously tho.. I wish they would do.01 ect updates for most of these updatesI know. It annoys me that browser devs keep changing the version number but I can't see a bit of difference on the UI.
    Reply
  • bennaye
    RandomactsChrome 18 does your homework!!!...Seriously tho.. I wish they would do.01 ect updates for most of these updates
    I wistfully think Google does this to rub it into the faces of Mozilla. FF got canned by the community for their "rapid-release-schedule-with-nothing-much-changed" strategy, while Google's doing pretty much the same thing but with *much* less criticism.

    Why don't people heap it on Google as well?
    Reply
  • nikorr
    Only the time will tell.
    Reply
  • Firefox and Opera already does that. But to answer your question - no. It sends nothing before you click a link.
    Reply
  • randomizer
    bennayeWhy don't people heap it on Google as well?Because most people see Google as a champion for the end user.
    Reply
  • come on...because google dont use the version number for marketing unlike mozilla!

    I dont even know what version im running or downloading without the about google chrome
    Reply
  • alidan
    JOSHSKORNI know. It annoys me that browser devs keep changing the version number but I can't see a bit of difference on the UI.i wish microsoft was like this, you know, change the engine without changing the interface. I get use to how something works (everything pre vista) than it all gets changed for no real reason (win 7, cant speak for vista)
    Reply
  • Will this mean that internet will no longer be stuck in series of tubes(aka pipes)?
    ;)
    Reply
  • solipsism
    izmanqwill this makes testing web service using chrome frustating, since chrome will send request before we click a link:|
    That's not what HTTP pipelining means. Basically, if you have 10 CSS files all hosted on the same server, a pipelined browser will request all 10 through the same socket without waiting for the response to the first 9 before making the 10th request. It then reads each reply off the socket in order.

    Assuming a latency of N milliseconds, a non-pipelined HTTP/1.1 connection would save (9*N) milliseconds in this scenario. However, pipelining support in webservers isn't all that reliable - even with HTTP/1.1, a naive implementation of HTTP could end up mixing content from the requests together, so the hard part of the client implementation is error checking and fallback.
    Reply