Hi, On Wed, Apr 28, 2010 at 12:32 PM, Bertrand Delacretaz <[email protected]> wrote: > Hi Felix, > > On Wed, Apr 28, 2010 at 1:13 PM, Felix Meschberger > <[email protected]> wrote: >> ...Configuration could be something like: >> * Enable/Disable caching support functionality completely >> * List of URL (or resource path) regexps with their setup, e.g. >> ^/(apps|libs)\/.*=must-revalidate >> * Enabled/Disable support for eager 304 responses... > > Wondering if that info should rather be provided by an OSGi service - > the default implementation could be config-based as you suggest, and > people could then plugin their own caching strategies.
Well, there is of course room for improvement, one thing certainly is to provide some API to overwrite the Cache-Control header other than calling setHeader or addHeader (which are overwritten to merge script provided Cache-Control setting with preset settings). Regards Felix > > Apart from that I like the idea, and like Carsten think that if that > can be done without using a Filter that might be easier. > > -Bertrand >
