-----BEGIN PGP SIGNED MESSAGE-----
Alexander Limi wrote:
> On Mon, 05 Sep 2005 22:20:02 +0200, Geoff Davis <[EMAIL PROTECTED]> wrote:
>> Alternatively you can create a function that checks the modification
>> for the content and for all portlets as well. Embed that composite time
>> in your ETag and you're all set. ESI would be cool, too, but I'm not
>> betting that we'll see that any time soon.
> The new PlonePortlets infrastructure could help here too, the plan is
> to have built-in caching parameters for each portlet here - so it can
> know whether it has fresh content or not, and feed that to external
> mechanisms like the ETags.
> Still science fiction, though. ;)
> (And before you ask - yes, we're putting it in the Collective shortly. :)
FYI, we have a portlet cache implementation on CPSPortlets tied with the
CPS event service for the cache invalidation :
If you wanna check :
And the implementation over there :
And the ESI support on the portlet there :
We never tested it though in here ;) Maybe Jean-Marc ?
Feel free to ask questions on the cps lists if you feel like...
Julien Anguenot | Nuxeo R&D (Paris, France)
CPS Platform : http://www.cps-project.org
Zope3 / ECM : http://www.z3lab.org
mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests