Question about caching systems for Zope.
I'm new to Zope, and while I understand caching in general, I have 0 experience using it in Zope. But I have an idea about what I would want in a caching system, so I thought I would query here and see if any of you can tell me if Zope can do what I would like. Basically, I would like a caching system that allows you to control the caching rules for different parts of a document? For example, you can apply caching ruleset X to part 1 of the document "Apple", and caching ruleset Y to part 2 of document "Apple". The need for this is if I had a page that would look the same for most users, but display user information if it was a logged in user. I would want everything except the user information section to be cached for long periods of time, as the source of it wouldn't be updated for often. But the panel for the user information I would want cached for the duration of the user's session. So I'm just asking if Zope offers something like this, or if you have any recommendations for how to achieve a similar effect. Or if it isn't doable, how close can I get? Thanks very much, Alec Munro
On Thu, Jul 11, 2002 at 03:35:41PM -0300, Alec Munro wrote:
The need for this is if I had a page that would look the same for most users, but display user information if it was a logged in user. I would want everything except the user information section to be cached for long periods of time, as the source of it wouldn't be updated for often.
http://rproxy.samba.org/ -- that's the only thing I've heard of in this area, and I have no idea how well it would integrate into the normal Zope + Apache/Squid combination. -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
1. You could use a RAM cache manager to cache renderings of particular methods. This is less effective than using an HTTP cache, but helps. 2. If you really want to get fancy, you can make the HTML coming out of Zope largely the same for each request for any given URL. Put Squid in front of Zope. Put apache in front of Squid. Embed some PHP (or embperl or mod_python directives, or even server side include directives, whatever) in Zope's HTML output. Then register a handler in apache that gets called for each request, postprocessing the output. If the parts you want included are simple enough, this will scream. But if you need to call back in to Zope to get any of the content, it might be better just to let Zope render the dynamic parts. - C ----- Original Message ----- From: "Mike Renfro" <renfro@tntech.edu> To: "Alec Munro" <alec.munro@eoascientific.com> Cc: <zope@zope.org> Sent: Thursday, July 11, 2002 3:04 PM Subject: Re: [Zope] Question about caching systems for Zope.
On Thu, Jul 11, 2002 at 03:35:41PM -0300, Alec Munro wrote:
The need for this is if I had a page that would look the same for most users, but display user information if it was a logged in user. I would want everything except the user information section to be cached for long periods of time, as the source of it wouldn't be updated for often.
http://rproxy.samba.org/ -- that's the only thing I've heard of in this area, and I have no idea how well it would integrate into the normal Zope + Apache/Squid combination.
-- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
participants (3)
-
Alec Munro -
Chris McDonough -
Mike Renfro