[Tickets #10156] Re: Css is not updated
bugs at horde.org
bugs at horde.org
Sat Jun 4 19:30:47 UTC 2011
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/10156
------------------------------------------------------------------------------
Ticket | 10156
Updated By | Michael Slusarz <slusarz at horde.org>
Summary | Css is not updated
Queue | Horde Framework Packages
Version | Git master
Type | Bug
State | Not A Bug
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Rubinsky
------------------------------------------------------------------------------
Michael Slusarz <slusarz at horde.org> (2011-06-04 19:30) wrote:
> Correct. The CSS cache's lifetime is controlled entirely by the
> lifetime configuration parameter.
>
> It is my understanding (Michael Slusarz can correct me if I am
> wrong), that this was done to save on many, expensive file stat
> calls on each page load for css files that are very unlikely to
> change.
Yes, this was correct. The reasoning is that CSS will not be updated
by anything else other than application updates. Javascript can
potentially be updated by packages, so we can't rely on an
application's version.
I mentioned at the time I wrote this code that another css caching
mode could be implemented (similar to JS caching), but I don't have
the time/interest to add such a mode right now. In general, if
playing around/developing with CSS (or even JS), caching should be
entirely disabled.
More information about the bugs
mailing list