On 12 Sep 2005, at 17:12, Geoff Davis wrote:
On Sat, 10 Sep 2005 16:04:18 +0100, Jens Vagelpohl wrote:
Here's the result of my refactoring/rewriting for the tests in
question:
http://svn.zope.org/CMF/branches/geoffd-cachingpolicymanager-branch/?
rev=38439view=rev
Geoff, as the one with
On Thu, 08 Sep 2005 17:45:54 +0100, Jens Vagelpohl wrote:
All those tests run fine for me using your branch and a vanilla Zope
2.7.6. I'd make a wild guess and say it's your setup.
Could be. Did you try removing the lines in test_Template304Handling.py
that clean up the profile_registry?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
times
for the content and for all portlets as well. Embed that composite time
On Mon, 05 Sep 2005 12:30:47 -0700, Alec Mitchell wrote:
If you write your ETags in an appropriate way, this works beautifully for
views. Consider an ETag that consists of a string containing (1) the
content object's modification date, (2) the user name for the currently
authenticated user,
Chris McDonough suggested an interesting way to do a poor-man's ESI: use
Apache's server side includes.
That's an interesting idea. On the Zope side, you'd just have to set
up your templates to spit out html containing SSI directives, obviously
no problem.
But what's involved in the Apache
On Mon, 05 Sep 2005 22:20:02 +0200, Geoff Davis [EMAIL PROTECTED] wrote:
Alternatively you can create a function that checks the modification
times
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
On Tue, 06 Sep 2005 05:39:45 +0200, 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
times
for the content and for all portlets as well. Embed that composite time
in your
