It is so that the timestamps are all the same, across all of your servers. If the timestamps are even a second off (which can easily happen when you are deploying to multiple servers), then the client will have to download the assets again every time their request hits a different server, which totally defeats the purpose.
- Jamis John Trupiano wrote: > Hey Jamis, > > I can't understand why we need to touch all of the asset files after a > re-deploy. If I understand it correctly, rails uses the last modified > date on an asset to append the querystring value. As such, this last > access date would change if a file was changed, but would otherwise > remain the same. What then is the need to go ahead and dirty all of > the assets? > > It seems to me that we're unnecessarily asking clients to re-download > all of our assets, even those that haven't changed. Am I missing > something here? > > Thanks. > > -John > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
