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. I would think that's unlikely to happen and could easily be solved by just changing the main file. The current problem is difficult to solve.
On Wed, Sep 11, 2013 at 9:16 AM, Thiago H de Paula Figueiredo < [email protected]> wrote: > On Tue, 10 Sep 2013 22:25:18 -0300, Howard Lewis Ship <[email protected]> > wrote: > > This is a tricky one to handle. >> > > Yep. I still couldn't find a good, simple solution yet. The whole > classpath asset support code is built on the top of the checksums. > > > It feels like we need yet another Asset URL path that works more like >> modules: no checksum in the URL and no far-future expires header, but >> maybe e-tags support. >> > > What about something like a "simpleclasspath" binding that does everything > the normal classpath one does but without the checksum? > > > Alternately, using the WYMeditor configuration, we could follow up on the >> idea I had on the user mailing list: an alternate asset URL that sends a >> proper redirect to the real asset. So /X/meta/wymeditor/foo.css would be >> redirected to /assets.gz/meta/wymeditor/**abc123/foo.css. >> > > That's a good idea, but it wouldn't solve the problem I'm having now. > > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@tapestry.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
