Hi Howard, I wanted to know if there is a reason why Tapestry couldn't just answer the requests for assets independently of the requested version. I believe that it is better to answer with a newer version than to just not answering at all… In AssetDispatcher, this could be done by just processing the request when its path starts with RequestConstants.ASSET_PATH_PREFIX and then to generate the virtualPath by stripping from this constant to the next "/" (assuming there is a version in the middle, which will be true for all the URLs generated by Tapestry).
Could this cause problems in some way? Regards, Raul. -- View this message in context: http://tapestry-users.832.n2.nabble.com/Versioned-assets-tp5421811p6202030.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
