> 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 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
