> 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 t
-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
>> p
> 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
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
browser
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
> 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";
