LESUEUR Frédéric wrote at 2006-6-22 15:08 +0200:
>i have a question about the "_setCacheHeaders" methods inside this
>file CMFCore/utils.py.
>
>Why content is set to aq_parent and not the object itself ?
The model (underlying the caching policy manager) is that
templates (views) access content obj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22 Jun 2006, at 15:08, LESUEUR Frédéric wrote:
hello,
i have a question about the "_setCacheHeaders" methods inside this
file CMFCore/utils.py.
Why content is set to aq_parent and not the object itself ?
The test of a policy is make with parent
hello,
i have a question about the "_setCacheHeaders" methods inside this
file CMFCore/utils.py.
Why content is set to aq_parent and not the object itself ?
The test of a policy is make with parent of object not this object. If
i have a FSImage, the test is make with this context parent and no
ht
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
jens
- "CachingPolicyManager: Support OFS.Cache.CacheManager",
[Accepted] http://www.zope.org/Collectors/CMF/408
mhammond
- "Windows Developm
Tres Seaver wrote:
Florent Guillaume wrote:
It might be possible to monkey patch only _checkPermission.func_code,
which seems to work on simple tests, but I've never tried it in real
life:
>>> def f(a):
... print a+1
>>> def g(b):
... print b+2
>>> f(0)
1
>>> f.func_code = g.f
