Hi Michael,

This caches only the resource version, e.g. message digest, but not the
actual contents of the resouce.

Kind regards,

Thomas


On Mon, Jun 17, 2013 at 4:02 PM, Michael Haitz <michael.ha...@1und1.de>wrote:

> Hi Thomas,
>
> it depends on your deployment mode:
>
>  if (application.usesDevelopmentConfig())
> {
>         // development mode:
>         // use last-modified timestamp of packaged resource for resource
> caching
>         // cache the version information for the lifetime of the current
> http request
>         resourceVersion = new RequestCycleCachedResourceVersion(
>                 new LastModifiedResourceVersion());
> }
> else
> {
>         // deployment mode:
>         // use message digest over resource content for resource caching
>         // cache the version information for the lifetime of the
> application
>         resourceVersion = new CachingResourceVersion(new
> MessageDigestResourceVersion());
> }
>
> best,
> Michael
>
>
> Am 17.06.2013 um 15:21 schrieb Thomas Heigl <tho...@umschalt.com>:
>
> > Hi all,
> >
> > I was wondering if Wicket has a built-in mechanism for caching the
> > generated byte[] of package resources. I use concatenated resource
> bundles
> > that are compressed using the YUI CSS/JS compressors.
> >
> > Using the default settings, compression is performed for every request
> that
> > does not have it in the client cache. Since this compression is a very
> > complex operation I'd like to perform it only once.
> >
> > Cheers,
> >
> > Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Reply via email to