Mike, Roberto, Have you folks heard of the W3C project called HTTP-NG, back in 1997-2000? Among other things, we developed a MUX protocol to use over TCP that multiplexed 128 connections in each direction, and greatly accelerated HTTP 1.1 pipelining. We also proposed a new data transfer protocol, which optimized data transfer over the links.
The project report is at http://www2.parc.com/isl/members/janssen/pubs/www9-http-next-generation.html. Our key test was downloading a complicated page: ``This page had been developed as part of earlier performance testing work with HTTP 1.1 [HFN97]. Called the "Microscape site", it is a combination of the home pages of the Microsoft and Netscape web sites. It consists of a 43KB HTML file, which references 41 embedded GIF images (actually 42 embedded GIF images, but in our tests the image "enter.gif" was not included, as libwww's webbot did not fetch it as a result of fetching the main page). Thus a complete fetch of the site consists of 42 HTTP GET requests. Our base performance measures were the time it took to fetch this page, and the number of bytes actually transferred. We repeated this test with HTTP 1.0, HTTP 1.1, and HTTP-NG.'' We demonstrated that using single mux'ed connection was faster, and reduced the number of bytThe <a href="http://www.w3.org/TR/WD- mux">HTTP-NG WebMUX protocol</a> was quite carefully designed; you might want to read through it, or even consider adopting it.es transfered by about 50%, which would accord with the speed-up in page- load times you are seeing. Bill -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
