Cezary Biernacki wrote: > > On Thu, Mar 24, 2011 at 12:04 AM, Thiago H. de Paula Figueiredo < > thiag...@gmail.com> wrote: > > > Why don't you set the application version symbol of your application > to a > > given value and never change it? > > > Really? It will cause all caching problems that version numbers are > supposed > to solve, will not it? > > Cezary > >
That's exactly what I was going to say ;) the far future expire dates Tapestry shows for all assets is a great way to maximize caching, and the version number is also a great solution to force clients to get the new version of your scripts/css/images, so a fixed version value is not a feasible solution. The solution proposed by Martin sounds very good, a redirect to the "current" URL of the asset. In fact, with HttpServletResponse.SC_MOVED_PERMANENTLY search engines should also update its references. Maybe none of these are ideal solutions, but my point is, to my understanding, redirects to current versions is a better solution than a not found. Regards, Raul. -- View this message in context: http://tapestry-users.832.n2.nabble.com/Versioned-assets-tp5421811p6202349.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
