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

[EMAIL PROTECTED] wrote:
> Jens Vagelpohl wrote at 2006-10-11 12:03 -0400:
>> ...
>> I'm not sure this can be called a bug. It is true (and perfectly  
>> normal) that rendering a filesystem page template will always call  
>> the CPM. You're rendering both here. Since output_page_2 is rendered  
>> last as it's calles from output_page_1 the rule for output_page_2  
>> fires and will overwrite existing headers/add new headers according  
>> to the rule that fires. The problem here is that both happen in the  
>> same request, the rendering code does not distinguish betwen the  
>> primary and the nested rendering.
> 
> 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.

This problem is actually the reason why having the RAM cache and the
HTTP cache header manager implement the same interface is broken:  they
are separate concerns.  The fact that they both involve caching created
a false sense of generality.


Tres.
- --
===================================================================
Tres Seaver          +1 202-558-7113          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFL95S+gerLs4ltQ4RAl/hAKDCPR3yZfDLmKcFDTy882gfisO5gACfSOMH
SGNxLObx+JhknmUV28f5lEY=
=fBkj
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

Reply via email to