Would it be possible to calculate the checksum for certain folder (and subfolders) and let the developer decide if it is more appropriate to use per file or per directory checksum?
Ville -----Alkuperäinen viesti----- Lähettäjä: Thiago H de Paula Figueiredo [mailto:[email protected]] Lähetetty: 12. syyskuuta 2013 14:55 Vastaanottaja: Tapestry development Aihe: Re: [5.4] Problems with the asset checksums and relative paths based on them On Wed, 11 Sep 2013 19:41:40 -0300, Barry Books <[email protected]> wrote: > Perhaps a dumb question but why does the checksum need to match for > Tapestry to return the file? The only problem I can think of is if the > included file changes but the main file does not then the cached file > might be used. What do you mean by included file and main file? > I would think that's unlikely to happen Actually, browsers not getting updated JS, CSS and image files after they were changed in the server is quite common without some mechanism like that. In T5.1 projects, many times I've had to ask the testers to clear their caches because they were testing the fix and the problem was still appearing because of the browser cache. I've actually fixed my problem by creating a request filter that checks for requests to files dynamically included by WYMeditor, find the original files in the classpath, generate a new Asset instance for them (which contains the right checksum) and redirects to it. Ugly, but fixes the problem. :) -- Thiago H. de Paula Figueiredo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
