Re: Tomcat relative path
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 5/28/2009 9:25 PM, Caldarale, Charles R wrote: From: tcwarrior [mailto:sr_s...@yahoo.com] Subject: Tomcat relative path 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. There are actually some things you can do on the server-side that will affect the parallelism of requests (okay, technically, it's the response content that controls it, not that the server is controlling the browser). See these resources for an interesting read: http://www.stevesouders.com/blog/2009/04/09/dont-use-import/ http://www.stevesouders.com/blog/2009/04/27/loading-scripts-without-blocking/ http://www.stevesouders.com/blog/2009/05/12/sharding-dominant-domains/ http://www.stevesouders.com/blog/2009/05/18/flushing-the-document-early/ I'm sure there are other tricks that can be done, too. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkopgIYACgkQ9CaO5/Lv0PAUhwCcCXaN5Dssbkh+XVnFJpeZ9nY1 TZgAni+gyWRtOjA2eRd52xXdNJ8DXVd0 =Gy95 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat relative path
From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: Tomcat relative path See these resources for an interesting read: http://www.stevesouders.com/blog/2009/05/12/sharding-dominant-domains/ Yes, it was the sharding one that the OP was trying to use, but that wasn't at all clear from the original message. - 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.
Re: Tomcat relative path
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
RE: Tomcat relative path
From: tcwarrior [mailto:sr_s...@yahoo.com] Subject: RE: Tomcat relative path Isn't it 2 per domain? Maybe; I didn't realize your intent was to have a separate domain for each image. If the client keeps track of connections by domain name, then putting pairs of images in separate subdomains will work; if the connections are tracked by IP address, it won't. Why wouldn't you want your site to be the most responsive and allow for parallel downloads? As Tim pointed out - bandwidth. You may well be dedicating the entire wire to a single client for a short period of time. That may or may not be acceptable. As for our dev team, why are they right? What is so hard about changing the source? It's a maintenance problem, as images come and go as the web pages are updated. You can certainly split the locations based on some scheme, but it adds much complexity to testing and deployment. - 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
Tomcat relative path
First off I'm very new to Tomcat so I'll apologize if the question seems entirely dumb. Here is our scenario: 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. We had a consultant tell us since we have 49 images loading on our homepage we should change this so parallel downloads occur. Our web development staff said it'd be too hard to change. 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? -- View this message in context: http://www.nabble.com/Tomcat-relative-path-tp23772234p23772234.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
RE: Tomcat relative path
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
RE: Tomcat relative path
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
