Hi, I use 4.4.1 meanwhile and this issue is fixed.
I feel your solution is even better than GWTs strong name approach. Numbers from my site: first page: 140KB second page: 5KB third page: 2KB Stefan Bachert http://wwwapp.de ________________________________ Von: Philipp Bärfuss <[email protected]> An: Magnolia User-List <[email protected]> Gesendet: Dienstag, den 21. Dezember 2010, 12:34:07 Uhr Betreff: Re: [magnolia-user] no caching >> magnolia 4.4 produces html-elements like this >> <script type="text/javascript" >> src="/resources/templating-kit/js/all.1291665377602.cache.js"/> Sorry for MGNLSTK-722, but now that this is fixed it is quite cool as it allows browsers to cache js and css (themes) for ever. Few insights: - The timestamp is the modification date of the resource (new file -> new timestamp) - the browser cache policy sets far future expiration headers (one year) for urls matching *.cache.ext patterns We will try to drive this one step further: - same trick for theme images - use the timestamp for produced images This will allow to reduce the traffic to Magnolia instances dramatically, esp. if you have a caching apache in front. Philipp ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
