I would create a custom tag to replace the image jsp tag. Then at configuration time, the custom image tag would write out the full url with whatever hostname you need so you can split your requests across domains.

Splitting requests across domains may speed up the requests on "legacy browsers" like IE6 which limit 2 open connections per hostname. IE8 no longer has this constraint. But it does nothing to help with bandwidth issues.

If many of the 49 images are shared on the rest of the site as general navigation structures, then keep them. Otherwise - look into combining some of them and use image maps which should reduce time to load.

[There are crazier alternatives - but they would be maintenance nightmares.]

-Tim

Caldarale, Charles R wrote:
From: tcwarrior [mailto:sr_s...@yahoo.com]
Subject: Tomcat relative path

Our tomcat servers are front ended by apache. The apache servers
do serve the static content. The img source is something like
/imagedir/pic.jpg which tomcat controls.

Not quite sure what you mean by "controls"; are you saying the web pages that hold 
the <img> links to the images are created by webapps running inside Tomcat?  (Probably 
doesn't really make a difference; I'm just curious.)

We had a consultant tell us since we have 49 images
loading on our homepage we should change this so parallel downloads occur.

I hope you didn't pay that consultant very much.  All web browsers make 
concurrent requests for images, style sheets, applets, etc., that are embedded 
in web pages.  However, unless tweaked, most browsers limit the concurrency to 
two - as recommended by the HTTP RFC.  Nothing you do on the server can change 
that.

web development staff said it'd be too hard to change.

They're right about that, but they should also know it won't make any 
difference.

My question is, is there an easy way to switch or do you have to change the img src to be http://image1.domain.com/imagedir/pic.jpg?

Unless each <img src> references a different server, it won't matter.  The 
browser concatenates links without a domain to the domain of the current page, so the 
end result is the same by the time the client puts the request on the wire.

 - Chuck


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to