Chrome 17 Gets HTTP Pipelining
There is a new feature that has just popped up in the Webkit snapshot releases of future Chrome versions, also known as Chromium releases. Chromium 17 includes an HTTP Pipelining flag.
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.
Pipelining can be enabled via a flag in chrome://flags and will result in Chrome sending off multiple http requests before a response is received. The purpose is to shorten load times of pages especially on slow client-server systems. The improvement is very limited at this time and highly subjective. Google is unlikely to offer this feature for customization, but indicated that Chrome will automatically select the best number of pipelines. There is no proxy support and there is no way for the system to deal with servers that do not support pipelining or incorrectly implement pipelining. Google said that it will be fixing this feature in the future.
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.
- Deals Oct 20: Dell 1130 Mono Laser Printer $54 FS
- U.S. and China Bicker Over China's 'Great Firewall'
- ARM Reveals Cortex-A7 Chip, big.LITTLE Processing
- Opinion: Intel is Underestimating ARM
- Logitech M525 Wireless Mouse Boasts 3-year Battery Life
- FSF Campaigns Against Windows 8's Secure Boot
- Logitech Now Offering Modern Warfare 3 Peripherals
- U.S. Advises Secure Control Systems Against Anonymous
- ARM-powered Ubuntu 'Webbook" Launches in South Africa
- Report: Microsoft Interested in Buying Yahoo Again
- Nvidia Confirms Tegra's 'Superhero' Roadmap
- Why We Can't Count Windows Out of the Tablet Game
- Seagate: Terabyte Platter HDDs Now in Volume Production
- Sony Launching Ultrabook in December Says Intel
- Deals Oct 21: Dual 24" Dell 1080p LED HDMI LCDs $360
- Blizzard Announces 4th WoW Expansion: Mists of Pandaria
- Winners of the Upgrading and Repairing PCs Book
- RAGE Issues Have Some Wondering About DOOM 4
Chrome 18 does your homework!!!...
Seriously tho.. I wish they would do .01 ect updates for most of these updates
Seriously tho.. I wish they would do .01 ect updates for most of these updates
I know. It annoys me that browser devs keep changing the version number but I can't see a bit of difference on the UI.
Chrome 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?
will this makes testing web service using chrome frustating, since chrome will send request before we click a link :|
Only the time will tell.
Firefox and Opera already does that. But to answer your question - no. It sends nothing before you click a link.
Why don't people heap it on Google as well?
Because most people see Google as a champion for the end user.
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
I 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)
Will this mean that internet will no longer be stuck in series of tubes(aka pipes)?
will 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.
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)
You do realize you can make win 7 look almost EXACTLY like winXP if you want to right? Was the same thing with Vista, you could choose your theme and layout and make it look so close to a WinXP you'd be surprised.
It's the MS Office that makes huge interface changes each release, and you have to re-learn how to write a document each release. That kinda blows, and their is no way to change the interface to look like previous versions of Office.
google de-emphasizes the number. since it auto-updates...and you don't even know the number unless you go out of your way, no-one cares.
...and, they've been rapid-release since inception. so who can complain...not like they 'jumped on board' after conventional released for a long time.
You do realize you can make win 7 look almost EXACTLY like winXP if you want to right? Was the same thing with Vista, you could choose your theme and layout and make it look so close to a WinXP you'd be surprised.It's the MS Office that makes huge interface changes each release, and you have to re-learn how to write a document each release. That kinda blows, and their is no way to change the interface to look like previous versions of Office.
i am looking into this, but i don't have the means to play around with the os yet, as both pcs we have are not mine with 7 on them. if i can get it exactly like xp, and i mean everything, i would get it, 2 new 2tb hdds, and a new motherboard for ddr3 and 16gb or ram. currently have a ddr2 build because i couldn't pay for new everything when my old pc died. had to make a new on out of the surviving parts.
This will be interesting to check out.
So far though I haven't been that well interested in Google's chrome ever since Mozilla's Aurora came out.
Because most people see Google as a champion for the end user.
Google doesn't put the version number out front & center. My wish is for all browsers to auto-update/prompt-to-update both the browser itself and its various extensions/plug-ins and have the capability to push-button enable/disable web features like java & flash, etc.
Something like this is a .1 release to be honest.
All you have to do is type this in the target field of your Chrome shortcut-
--enable-http-pipelining
It works!
For all things tech, visit my channel: youtube.com/supershamrock1234
I know. It annoys me that browser devs keep changing the version number but I can't see a bit of difference on the UI.
Who in the world cares about the UI? It could be a UI from the late 90s and it wouldn't matter very much. What matters is the stuff under the hood; the ability of the browser to properly translate HTML, CSS and Javascript into a user experience. Everything else is secondary.
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?
Methinks you don't know much about the web and computer science.