This is an interesting problem; a significant proportion of a dynamic website is not driven by the user requesting a page, but is rather driven by certain triggering conditions. In an ideal world, you be able to write your website as a dynamic website, and some kind of magic would determine what the conditions triggring the rendering of a page were and then set up some kind of notification mechanism to cause the re-rendering of the page as the conditions are triggered. For example, a news page only needs to be re-rendered when the news on the page changes. Being able to identify which parts of a page need to be re-rendered is even more fine-grained. To do this, youd have to timestamp virtually every single object, from variables on up, with a last-modified date. This could be tricky. ----- Original Message ----- From: Christopher Petrilli <petrilli@digicool.com> To: Paul Mokbel <pm@webhosting.com>; <Zope-Dev@zope.org> Sent: Sunday, September 12, 1999 9:54 PM Subject: Re: [Zope-dev] Caching

...

In ROXEN (RXML); There is a tag line where by you can cache certain content within the <CACHE> brackets. Is there something similar within Zope?

What has been thought of is doing more "rendered caching" (i.e. cache rendered results, thereby short-circuiting the DTML process). This could be very advantageous, but gets into a lot of issues of management of the cache which is non-trivial (Vignette, one of our competitors that does "consultant-ware" has several patents on it), so... patches accepted. Note that performance will be one of our "watch words" in the coming months.

Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli@digicool.com http://www.digicool.com

_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://www.zope.org/mailman/listinfo/zope-dev

(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce

For non-developer, user-level issues, zope@zope.org, http://www.zope.org/mailman/listinfo/zope )