Hi,

I've been wondering about this for some days and tried out several
things, but none of them really did the trick for me, so I decided to
ask you for help.
In my T5 webapp, I have some configurable data, namely consisting of an
ID, a CSS color code and localized descriptions. This information is
used by a couple of pages and rarely changes, so I thought it best to
serve it as a JSON object in a separate JS file which can then be
@Import'ed in the pages where I need it and cached and re-used by the
browser.
As the content is configurable from within the application, I know when
the content has changed, so I can adapt the URL and force the browser to
load the new content.
I already tried two approaches - by implementing a Dispatcher and an
AssetFactory (which seems the right direction to me), - but neither
seemed to feel absolutely right. I'm aware that there probably won't be
the *one way* to do it, but maybe you could give me some insight on how
that would be best accomplished.
Thanks in advance for your help.

Regards,
Jochen


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to