Again no disrespect - I too am all for easier maintenance on the server side, but don't fall into the trap of thinking that your files will be cached just because the URL doesn't change.
I have just made several requests to your site all the (index page) and each time your CSS was downloaded (while your images cached). I have had this problem in the past (but with a different SSI language) and came to the conclusion that the HTTP headers are missing details which makes the browser cache the page (eg. Last-Modified, Etag, Content-Length). Files which are built on the fly (eg. ASP, PHP) do not cache well as the file is always "new". You maybe able to get around this by forging the HTTP headers your server sends but this can be a difficult task. A simple solution, which the www.optusnet.com.au website uses, is to break the large dynamic stylesheet up into smaller static ones and use the "cascading" ideal of the language to make your skin changes. A handy tool to check how well your site caches is at http://www.web-caching.com/cacheability.html I know this is way off topic for this list but I wanted to alert the many designers of this problem as it is a common mistake. ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
