On Wed, 2009-02-25 at 13:30 +0100, Philippe Marschall wrote: > Jan Haderka wrote: > > > >> Is there a way to configure cache so that a new added network is not > >> cached by default? > > > > Unless you are doing some redirection of the content the bypass for > > cache filter should do the trick. > > What's the advantage of this over adding a deny voter in the cache policy?
Hmm, good question. Let's see: adding bypass on cache filter: - "failing" as soon as possible (less code executed, faster) - all cache policies/executors in a chain are bypassed adding deny voter on cache policy - "failing" further down in the chain. - more specific/finer grained - applies only to server cache, and leaves other parts of cache to deal with the content their own way (e.g. browser cache policy FixedDuration would still return that content can be cached on the client for given duration if executed). ... could be more, but I think the above are the main differences. I suggested filter bypass, because it was the place where i would look for solution to such problem by gut feeling first, not because i could think of any really obvious advantage of such approach. Jan > > Cheers > Philippe > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- -- Best regards, Jan Haderka Magnolia International Ltd. ---------------------------------------------------------------------- [email protected] http://www.magnolia-cms.com Magnolia® - Simple Open Source Content Management ---------------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
