L
Larry Marburger
I've built an XSLT that is used to generate a simple TreeView-type,
web-based control (ASP.NET / C#). When the tree is fully transformed
(client-side, JavaScript transformation), there are about 5 different
images that are referenced (page.gif, folder.gif, plus.gif, minus.gif,
and clearpixel.gif). What I assumed would happen would be that once it
loads page.gif, every place in the transformed HTML document that
references page.gif would load at the same time. However, what really
happens is the client will request the image page.gif for each and every
instance of page.gif on the resulting HTML document.
As it stands now, the tree has 600+ nodes. This results in 5 separate
images on the page, but ~2,400 image requests. This is, obviously,
highly unacceptable.
Any ideas about how to minimize the amount of image requests sent to the
server?
web-based control (ASP.NET / C#). When the tree is fully transformed
(client-side, JavaScript transformation), there are about 5 different
images that are referenced (page.gif, folder.gif, plus.gif, minus.gif,
and clearpixel.gif). What I assumed would happen would be that once it
loads page.gif, every place in the transformed HTML document that
references page.gif would load at the same time. However, what really
happens is the client will request the image page.gif for each and every
instance of page.gif on the resulting HTML document.
As it stands now, the tree has 600+ nodes. This results in 5 separate
images on the page, but ~2,400 image requests. This is, obviously,
highly unacceptable.
Any ideas about how to minimize the amount of image requests sent to the
server?