XML Method Cache Manager - Add : Create a Cache Manager XML Method Cache Manager is a Zope object that caches the results of processing done by a set of xxxMethod objects (only XSLTMethod as of today). A particular Cache Manager serves the set of xxxMethod instances within its parent folder and all subfolders (its clients). In contrast to Zope's built-in caching objects, XML Method Cache Manager is specialized for use with xxxMethod objects. That is, it will notice when either an XML source object or XSLT transformer object have changed, and invalidate the cache file representing the results of that particular transformation. Also, the CacheManager stores cached content in the filesystem, *not* in the Zope object database. By default, XSLTMethod never caches its results. However, XSLT processing is expensive. In the real world, there is generally no need to transform the content every time except in rare circumstances such as when the XML content is retrieved from a database on the fly and changes dynamically. For all but these rare circumstances, caching can improve performance considerably. This is what CacheManager is for. An xxxMethod object searches for a CacheManager instance via acquisition. That is, it looks for it in its parent folder, than its parent's parent, on up the tree to the root folder, and stops when it finds the first one. A CacheManager is a purely optional thing. Removing one will *never* break anything -- it is purely an optimization, because XSLT transformations (or other XML processing) can be expensive. Every xxxMethod object has a "caching behavior" property. This controls whether caching should be done *if* a CacheManager is present. If a Cache Manager is *not* present, caching will never be done, regardless of the setting of the property. The property is there to guard against those situations where caching is *never* appropriate, such as when dynamic content is obtained from a database as described above. If an xxxMethod "caching" property is set to "on" *and* a CacheManager is present, caching will be done. A Cache Manager stores the results of transformations in files on the disk, as specified in the *cachePrefix* property. Optionally, a Cache Manager may also perform other functions on its client XSLTMethod objects. These functions may be either invoked programmatically or from the Cache Manager's "Cache" tab in the Zope Management Interface. See the readme and tutorial files for more information. Entry Fields 'Zope ID' -- The standard Zope object identifier. This must not be left blank. 'Title' -- The optional title of the cache manager object. 'Description' -- The optional description of the cache manager object.