[Zope-CVS] CVS: Products/PluggableAuthService/doc -
jens at dataflake.org
Mon Nov 8 04:18:07 EST 2004
Update of /cvs-repository/Products/PluggableAuthService/doc
In directory cvs.zope.org:/tmp/cvs-serv9211/doc
- revert to use RAM Cache Manager, which will receive the improvements
that the PAS RAM Cache Manager had
=== Products/PluggableAuthService/doc/caching.stx 188.8.131.52 => 184.108.40.206 ===
--- Products/PluggableAuthService/doc/caching.stx:220.127.116.11 Mon Nov 8 02:13:38 2004
+++ Products/PluggableAuthService/doc/caching.stx Mon Nov 8 04:17:37 2004
@@ -10,12 +10,12 @@
Given a plugin that is cache-enabled the steps to using the cache are
easy. The site administrator needs to...
- o Instantiate a "PAS RAM Cache Manager" inside the PluggableAuthService
+ o Instantiate a "RAM Cache Manager" inside the PluggableAuthService
o Using the "Cache" tab in the cache-enabled plugin's ZMI view,
- associate the plugin with the PAS RAM Cache Manager
+ associate the plugin with the RAM Cache Manager
- At this point values will be cached inside the PAS RAM Cache Manager. The
+ At this point values will be cached inside the RAM Cache Manager. The
effect can be viewed easily on the "Statistics" tab in the Cache Manager
ZMI view, which shows which plugins have stored values, how many values
are stored, an approximation of the memory consumption for the cached
@@ -28,7 +28,7 @@
The PluggableAuthService itself is also cacheable this way. Caching PAS
itself is the easiest way to achieve caching. In PAS, the _findUsers and
_verifyUser methods, being a suitably central spot for caching, have
- been enhanced to use the PAS RAM Cache Manager if so configured.
+ been enhanced to use the RAM Cache Manager if so configured.
How does a plugin programmer use it?
More information about the Zope-CVS