Closed adetwiler closed 12 years ago
IMO this is an issue that is better dealt with at the server level with Apache (or w/e) cache and expiration headers.
Reason being, filemtime and other file stat functions are going to result in a disk read for every single request. This could be mitigated somewhat with some sort of memcache intermediate, but that would defeat the purpose of the intended functionality (to ensure an always-live file).
ok cool :) best to not use that much disk reads.
On Wed, Jan 4, 2012 at 9:40 PM, Thom Stricklin < reply@reply.github.com
wrote:
IMO this is an issue that is better dealt with at the server level with Apache (or w/e) cache and expiration headers.
Reason being, filemtime and other file stat functions are going to result in a disk read for every single request. This could be mitigated somewhat with some sort of memcache intermediate, but that would defeat the purpose of the intended functionality (to ensure an always-live file).
Reply to this email directly or view it on GitHub: https://github.com/thomshouse/escher/issues/28#issuecomment-3365572
In addLink and addJS maybe have something similar to this: (the 2nd answer), or maybe you might have a better idea.
http://stackoverflow.com/questions/118884/what-is-an-elegant-way-to-force-browsers-to-reload-cached-css-js-files