[petrol]

I was talking to the guy at work today who runs our web server. We were testing out a major update to the site, and from looking at the stats from the web server we noticed that each time one of us connected using Safari, the browser opened a new connection to the server to download each image on the page, but if we went to the page in IE, there was only one connection to the server.

We are still both using Safari 85.5 (haven't upgraded to Panther at work yet), so I don't know if that changes in 100.

Can anyone confirm this, or explain why it is? We never noticed before, because not many people here are using Safari yet and the old version of the website was not very graphics intensive, but the server software is set (by default) to only allow 36 connections at a time, so it causes problems when more than one person views the site at a time.

[Ludovic Hirlimann]

Originally posted by petrol:


We are still both using Safari 85.5 (haven't upgraded to Panther at work yet), so I don't know if that changes in 100.

Can anyone confirm this, or explain why it is? We never noticed before, because not many people here are using Safari yet and the old version of the website was not very graphics intensive, but the server software is set (by default) to only allow 36 connections at a time, so it causes problems when more than one person views the site at a time.

Are you running IIS ? that might be the reason why you don't see more then one connection.
As for why browser since mosaic 2.0 or Netscape 0.90 do open one connection per image is jus for speed.
In the early days browser would download entirely the html page - parse it and when they find an image statement would request sequentially the image, a page with 3 or Four graphics would take a minute or more to load. To speed up things, modern browser do parse the stream of the html page (and find the images tags), and for each images tag open a connection so the page renders faster.

btw 36 is really to small.