[ZDP] BackTalk to Document The Zope Book (2.5 Edition)/Using Basic Zope Objects

webmaster@zope.org webmaster@zope.org
Wed, 25 Sep 2002 15:30:02 -0400


A comment to the paragraph below was recently added via http://www.zope.org/Documentation/Books/ZopeBook/current/BasicObject.stx#2-103

---------------

    A *cache* is a temporary place to store information that you
    access frequently.  The reason for using a cache is speed.  Any
    kind of dynamic content, like a DTML page or a Python Script, must
    be evaluated each time it is called.  For simple pages or quick
    scripts, this is usually not a problem.  For very complex DTML
    pages or scripts that do a lot of computation or call remote
    servers, accessing that page or script could take more than a
    trivial amount of time.  Both DTML and Python can get this
    complex, especially if you use lots of looping (such as the 'in'
    tag or the Python 'for' loop) or if you call lots of scripts, that
    in turn call lots of scripts, and so on.  Computations that take a
    lot of time are said to be *expensive*.

      % Anonymous User - May 27, 2002 7:18 pm:
       I think the topic of caching should be introduced at a later 
       chapter. A user new to Zope has other problems than caching 
       when he reads this chapter.

      % Anonymous User - June 5, 2002 5:16 pm:
       also... is this server-side caching or client caching?

      % Anonymous User - Sep. 21, 2002 6:07 pm:
       what is a "trivial amount of time" ?
       /trivial/tolerable/

      % Anonymous User - Sep. 25, 2002 3:29 pm:
       The author is talking about server-side caching.