Isn't it 2 per domain? Nothing stops image1.domain.com for being a cname for a subdomain. I must have not worded or phrased my question well. Why wouldn't you want your site to be the most responsive and allow for parallel downloads? No the consultant guy wasn't brought in for this, it was more of an fyi.
As for our dev team, why are they right? What is so hard about changing the source? If you spread downloads across say 3 servers which are all on their own subdomain, how would that not make a difference? Isn't it each would need to point to a different server? ex. have .gif's go to subdomain1 and .jpg's to subdomain2? 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 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 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 > > > -- View this message in context: http://www.nabble.com/Tomcat-relative-path-tp23772234p23773866.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
