On Fri, Feb 12, 2010 at 9:56 PM, Alex Black <[email protected]> wrote: > If this was implemented, it should be a unique id once per CSS change, > not once per application start. > > E.g. we deploy to production every few weeks, and client browsers > should be able to cache files that entire time until change them, > regardless of reboots. > > But obviously a value once per application start is much easier. > > I think what this points out is that its the file's datetime that is > the state that needs to be used here, and the existing mechanism of > HTTP looks like the way to go. Perhaps I'll dig into it and try to > understand why this is not working as one would expect.
Or just the MD5 hash of the contents... /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
