W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2004

Re: HTTP1.1 Proxy, clients multiple persistent connections

From: Robert Olofsson <robo@khelekore.org>
Date: Wed, 03 Mar 2004 01:04:09 +0100
Message-ID: <404520F9.309@khelekore.org>
To: Přemysl Kouřil <Premysl.Kouril@seznam.cz>
Cc: ietf-http-wg@w3.org

>why client makes new connections to proxy when another persistent connection between same client and same proxy exists. Thanks
One of the reasons is usually that you can start displaying the page if 
you have the top (of a long page)
and the images at the top.  If I remember correctly mozilla will not 
pipeline on the main connection
for a page (they will reuse the main connection as an ordinary 
persistent connection when the main
page is fetched). They do this since the page is normally large, and the 
images in it are many and small.
If they do not pipeline on the main connection, they want several 
threads to start getting the images
that are needed. 

If they can start display the page correctly  quick and load the rest 
with only the scrollbars updating
the user will think that the browser is faster giving a more happy user.
Of course the total time to download a page with images takes a bit 
longer for each extra connection,
but experienced user time is not equal to total time...

I may be wrong about how mozilla is doing  things now though, but I 
still belive that they do it like
this (or has tweakable options for this).

Received on Tuesday, 2 March 2004 19:04:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:37 UTC