I myself want the assets to be cached with a MD5 signature, so I don't
have to track explicit versions.. etc etc. (that's what we do right now
with our own AssetFactory, but we have not upgraded to 5.1..)
On 3/19/09 9:33 AM, Jack Nuzbit wrote:
I've just upgraded an application from 5.0.18 to 5.1.0.1 (a very smooth
upgrade i might add) and I'm very impressed with the new performance
features, gzipping and the far future asset headers.
I was wondering if anyone's considered adding the facility to use an assets
date modified in the cache url so they could stay cached over multiple
application versions. I would say 99% of assets remain the same over
different application versions so this would be a big win. I tried it out by
making a change to the ContextAssetFactory and the AssetDispatcher and it
worked very nicely.
Anyone have any thoughts on this?
Jack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
