Hi, but isn't it enough to send the correct cache headers + a calculated filename that contains the hash of file? I think caching on your container isn't the best option (using nginx or varnish or a CDN like Akamai or something similar is way better), else you've to compile each resource on all your containers and you need some heap space for the content.
best, Michael Am 17.06.2013 um 16:02 schrieb Michael Haitz <[email protected]> : > 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 <[email protected]>: > >> 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: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
