[GeneralDiscussion] Re: zope/plone article

On 7 Mar 2009 at 1:17, betabug wrote:

> I think the confusion arises because of your suggestion to use
> ``must-revalidate`` in the cache-control header. That is a good
> suggestion, but first, it would have to be optional (maybe combined with
> the Last-Modified setting) and second, no way am I going to agree to a
> hardcoded value for max-age just because we want to set
> ``must-revalidate``. Different sites may have vastly different notions
> of what is an acceptable value for max-age - if they want it set at all. 

That's definitely where the confusion was arising - I had taken it 
from your original email that you didn't want conditional GET fixing 
because you felt adding Accelerated HTTP Cache Manager support was a 
superior solution.

Now I have no idea whether adding support for it or not is hard. I 
was merely concerned with conditional GET working as intended.

> As I said before, the proper Zope way for the cache-control settings is
> to have these controls in an object where they can be set on a
> site-by-site basis. That's the way Plone does it (with their cache-fu
> tools), that's the way "Accelerated HTTP Cache Manager" is meant to be
> used. 

I do absolutely agree that the CacheFu approach is superior. It 
appears to use per-user unique cookie values in the HTTP headers to 
operate a per-user cache which persists across days (or even weeks) - 
very clever. It even seems to know when a page has been updated and 
which bits to expunge from the cache.

I don't even pretend to know how it works - I turned it on and 
watched the HTTP headers and it's outstanding. TBH before CacheFu I 
wasn't even aware HTTP 1.1 had such abilities.

Cheers,
Niall


--
forwarded from http://zwiki.org/GeneralDiscussion#msg49B248B6.8767.DCE92B5@s_sourceforge.nedprod.com