Seems to me that your are on the right track. 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.
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. On Thu, Sep 9, 2010 at 11:32 PM, Jochen Berger <foober...@googlemail.com> wrote: > Hi again, > > so at least this use case does not seem to be trivial. ;-) > But as the answers stay away, maybe it didn't become clear from my > explanations. If you'd tell me, which parts were not understandable, I > could try to rephrase them. > > Regards, > Jochen > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
