[Zope-CMF] CachingPolicyManager

Jens Vagelpohl jens at dataflake.org
Fri Oct 13 15:54:30 EDT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 13 Oct 2006, at 14:06, Dieter.Maurer at Haufe.de wrote:
> Thus, this *is* the bug. It should distinguish between primary and  
> nested
> rendering.
>
> Unfortunately, the bug is probably deep -- affecting the complete
> cache integration. Even more importantly, for a RAM cache it may
> even be a good thing that the "nested" rendering can cache in addition
> to the "primary" rendering.

Absolutely, RAM caches and similar caching mechanisms should still  
get a chance to do their work for both the requested item as well as  
sub-items that get called from the requested template.

Tres just had a good idea and I'll play around to see if this works:  
Before calling the CPM, see if REQUEST['PUBLISHED'] is the currently  
rendering item (in that case we want CPM), or if it is not, meaning  
we hit a sub-template and don't want CPM.

jens


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFL+72RAx5nvEhZLIRAiA/AJwIoy/nz0umpfY3B+NfRwEsMoTymwCghHRz
jUbkw0Rx0eA1DaCOGoFc5LY=
=GhT2
-----END PGP SIGNATURE-----


More information about the Zope-CMF mailing list