Chrome 17 will become the ninth version revision introduced in 2011 and has just been released as Chromium nightly version of the browser via Google’s Webkit snapshot release channel. This new version is the first to integrate http pipelining via a flag.
We have previously reported about this new feature and its availability via a switch, but Google recently added a flag that can be accessed via chrome://flags and activated by clicking the HTPP Pipelining checkbox.
While Firefox and Opera have offered pipelining for some time, Google has just recently added support for this technology that can dramatically speed up the load times of web pages, especially of those that are held down by significant latency connections. Pipelining refers to an approach in which multiple HTPP requests are sent before any responses are received. The effect is reduced network load and delivers potentially shorter load times, as long as the server the browser connects to supports this feature as well.
Google does not reveal how many simultaneous requests Chrome uses (Firefox, for example, enables users to determine the maximum number of requests), but we know that Google is very cautious about this feature for now.
This must be enabled in about:flags. It is naive and assumes all servers correctly implement pipelining. Proxies are not supported. The current implementation cautions users that not all servers correctly support pipelining and proxies are not supported at all. Until launch, Google said that it will add a capability to support proxies, detect broken transparent proxies and mitigate broken servers. Chrome will also be able to optimize itself to determine the best number of parallel http requests.
You can try this new feature by downloading a recent Chromium snapshot. The feature is integrated in the browser in build versions 106364 and higher.
Daniel Bailey in Products on October 20
No comments:
Post a Comment