Luke Lutman schrieb: > Ⓙⓐⓚⓔ wrote: > > making all the requests and at the top mimics the normal image load ... > > the only case where sequencing might help is when the server is > > configured strangely , or just can't handle the requests... (as in > > thousands of large graphics??). > > The page I wrote that snippet for was an image gallery (about full size > image, plus thumbnails). > The thumbnails and one image are visible when the page loads, and the other > full-size images are > shown when you click on the corresponding thumbnail. If I preloaded the 29 > hidden full-size > images on document ready, the page felt reeeeaaaalllly slow because it loaded > all the hidden > images before loading the ones that were visible! > > As far as the server benefits, imagine the page above being loaded by 30 > users at the same time. > Preloading the images sequentially only takes up 30 connections at any given > time. Preloading > them all at once could take up 870 connections! It might not make much > difference, but it > doesn't hurt, either ;-)
Apart from that, most browsers usually don't allow more than two open connections per host. Thus I think this solution is quite reasonable. You could make it preload two images at a time... -- Klaus _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
