You are right, that Arachne's still noticabe slower than Netscape. 
Paralell download of two images at once helped a lot, but Arachne now
needs "Keep alive" option. 

Historicaly, response of server to connection request used to be quite
fast, but as more and more browsers supported Keep-alive HTTP option, it
was no longer important to quickly respond to connection requests. And
connection request itself requires cca 3 extra packets to be negotiated
in both ways, so if some page contains 20 or more very small images, 
browsers which can't handle Keep-alive are in great disadvantage. 

Using of many small images is very common now, but in the begining, 
all web pages looked like Yahoo, ie. they used maximum number of 2-3 
images...

It should be relatively easy to add Keep-alive to Arachne, because
Arachne anyway uses only one pair of sockets allocated for all data
transfers....

--
Michael Polak: [EMAIL PROTECTED]
Arachne Labs: http://arachne.cz/
My mobile phone - up to 160 characters: [EMAIL PROTECTED]

Reply via email to