Howard, Am Freitag, den 10.09.2010, 09:08 -0700 schrieb Howard Lewis Ship: > In 5.2 there's an AssetDispatcher service that can be contributed to; > the built in contributions are for context assets, classpath assets, > and stack assets (i.e., aggregated JavaScript libraries). You can add > your own AssetRequestHandler.
Ok, I'll have another go at this approach then. I already tried it but unfortunately I can't remember why I gave it up. > You can look at some of the existing AssetRequestHandlers for an idea > of how to handle an infrequently changing asset ... perhaps have a > version id as part of the URL and increment it when the content of the > asset changes. Yeah, that's what I had in mind. Remember the last timestamp when the data changed and hex-encoding it into the URL, like what is done with zone updates. Thanks a lot, Jochen --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
