Ah, good to know. In my case, we're running on our own servers, so that isn't too big an issue. Also, we're using Java, and store the cache files in the webapp's temporary directory, and set them to delete on exit (java.io.File.deleteOnExit()), so they get trashed when we restart the server.
But thanks for pointing it out for those dealing with a shared hosting environment. --Erik On 8/15/07, Stephan Beal <[EMAIL PROTECTED]> wrote: > > On Aug 15, 11:32 pm, "Erik Beeson" <[EMAIL PROTECTED]> wrote: > > I cache the packed versions. Actually, I concatenate all of the scripts that > > I need for a page, minify them (used to use packer, now I use YUImin), and > > then cache that, all on the fly. So I have one script tag like: > > The problem with caching is that it fails on some hosting providers. > For example, if i did this on the SourceForge servers, the cached file > would be owned by some web user other than me, which means my account > cannot remove the file. Writing files from a web server is often > problematic vis-a-vis file access rights, especially when your account > is not the one which apache runs as. It is possible to tell apache, > with the right module(s?), to run each virtual host as a different > user, but it's not always possible to set this up (e.g. SourceForge > sites). > > >
