in reply to Javascript/CSS on the fly
Why are you varying the CSS or javascript?
If it's to deal with quirks in different web browsers, and you're trying to serve slightly different versions based on the browser, then I'd recommend that instead of generating the CSS or JS dynamically, you instead generate the references to the correct file dynamically, and have the files themselves be static (or not... see below)
As for the caching issues, you can manipulate things using the correct headers, such as 'http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9 Cache-control', you can get around things -- if it's possible that you might send different versions to the same browser (which is not the case when dealing with browser quirks), then you just need to make the URL formatted in such a way that the browser will consider them differently, while still using GET.
Instead of using a URL passing the info in QUERY_STRING:
http://www.example.com/cgi/generator?id
You should instead pass the date in PATH_INFO:
http://www.example.com/cgi/generator/id
With Cache-control, you can insure that the pages will be cached, and with the differing URLs, you can get the browser to treat different versions as seperately identifiable files.
I'd be interested in knowing exactly what it is that you're trying to accomplish -- there may be better solutions (eg, a 'main' css file, and some pages reference the main file + specific modifications for that page)
|
|---|