Didn't someone make a RAM Cache Manager with a max age thing? I swear I remember seeing it posted on Zope.org.
yes. someone did. but i discovered it a bit late, as i've replaced the 2.3.x StandardCacheManager with 2.4.x :P all's working now, i hope
The nuances of the cache manager baffle me as well, and I'll need to defer mostly to Shane, but I *think* that at least for the RAM cache the REQUEST variables listed are used as part of the key into the big "cache dict" where things are held.
This means that, if, for example, you've got AUTHENTICATED_USER as a request variable, if the AUTHENTICATED_USER is "fred" when you cache one page, another user "bob" won't see fred's cached page (which might contain his name). However you *will* still be able to cache the page for fred.. the next time you ask for the page, a customized "fred" version will be served from cache. The more variables that are different and listed, the more RAM will be consumed for slightly different versions of the same page.
ok. there's two places where we can define this. the cache manager, and the methods cache tab. consider this: -we define REQUEST variables AUTHENTICATED_USER at the cache manager setting we dont define anything at the method cache tab -or we have somevar as the REQUEST variables in the method cache tab, and only AUTHENTICATED_USER in the cache manager setting. there's so many combinations that boggles the mind.
There was recently a Zope-maillist posting by Sebas ICK that quoted Richard Barrett which goes in to some speculative detail about using Squid to front end for multiple Zopes. If it's accurate, it should really be cleaned up and turned into a howto.
http://aspn.activestate.com/ASPN/Mail/Message/906749 i need to relook at this. what i have now: __ zeo client ----------- | : | lvs --------| : |-----zeo server |__zeo client------------| so with squid in the picture, i guess it'd be before lvs ..? thanks to sean, i know what i missed when trying squid with zeos. a redirector. (the squid virtual stuff pulls me of track :))
I'd consider something like Squid to do the job of taking the load off your servers. It's a learning experience, but probably worth it for a site like yours.
i'll look into this. thanks all
- C