Friday, March 21st, 2008
Steve Souders has taken a step back, analyzed the blog content that came out of IE 8 supporting 6 connections per host, and has pulled together the facts to discuss:
Section 8.1.4 of the HTTP/1.1 RFC says a â€œsingle-user client SHOULD NOT maintain more than 2 connections with any server or proxy.â€ The key here is the word â€œshould.â€ Web clients donâ€™t have to follow this guideline. IE8 isnâ€™t the first to exceed this guideline. Opera and Safari hold that honor supporting 4 connections per server.
Settings for current browsers
Steve documents the browsers, and discusses how you can tweak the settings in your own: “Itâ€™s possible to reconfigure your browser to use different limits. discussion about increasing Firefoxâ€™s number of connections. In comment #22 Boris Zbarsky lays out a good argument for why this increase will have no effect on most servers. But in comment #23 Mike Hommey points out that persistent connections are kept open for longer than the life of the page request. This last point scares me. As someone who has spent many hours configuring Apache to find the right number of child processes across banks of servers, Iâ€™m not sure what impact this will have.
Having said that, Iâ€™m please that IE8 has taken this step and Iâ€™d be even happier if Firefox followed suit. This change in the client will improve page load times from the userâ€™s perspective. It does put the onus on backend developers to watch closely as IE8 adoption grows to see if it affects their capacity planning. But Iâ€™ve always believed that part of the responsibility and joy of being a developer is doing extra work on my side that can improve the experience for thousands or millions of users. This is another opportunity to do just that.
Posted by Dion Almaer at 10:10 am