http://techblog.molindo.at/2008/08/wicket-interface-speed-up-caching-resources-forever.html
-igor On Thu, Apr 16, 2009 at 4:20 AM, the_adam <[email protected]> wrote: > > Sorry for bumping, but this was never resolved and seems like an important > issue. > > > Jörn Zaefferer-2 wrote: >> >> Please stop mixing stateless and static. Thank you. >> > > Let's try not to. Any clue how to serve static content (i.e. javascripts) > that would be cacheable. I cannot imagine that Wicket team would see a > situation where i.e. jquery.js included by wickext project wouldn't be > cacheable as a proper one. In a situation as is all resources served by > plugins / components can only be cached while the session lasts. I would > call this as highly undesirable. > -- > View this message in context: > http://www.nabble.com/Wicket%2C-url-rewriting-and-shared-resources-browser-caching-tp20508529p23075867.html > Sent from the Wicket - Dev mailing list archive at Nabble.com. > >
