Caching is a very complicated issue. In the ideal world, the image would be cached in the browser and only loaded once, upon the first request. However, our forums specifically use "no-cache" headers to ensure that the latest version of the page is always loaded. If the sig image is hosted on an outside server and the image is requested in three posts, it is conceivable that your client does have to request that image file three times. This type of performance analysis and tuning is out of our control.

 

Exactly!! When my browser gets the code, it begins to load the page from all servers... but I'm trying to say my browser isn't even getting the code... the site 'hangs', then pushes down the html & other data to me in a huge rush. Thus, the percieved server issue.

 

See my post above (last one on page 1 for me) for a potential explaination of the partial HTML rendering...^^^

 

Very true. I oversimplified the concept. I host my sig off-site, so the individuals browser should only be getting it once... I assume everyone else does the same... opps!

 

Very intersting stuff. Thanks for the info and reading all my babbling.

 

Wrong, I go through 18.

 

Good info sorry for the large sig..

 

thanks for the IP address Joe.

 

I was thinking thte same thing. Plus, those Road Runner addresses don't cycle that often.. heh heh heh..