On Sat, Jul 29, 2006 at 11:02:10AM -0400, Chris McDonough wrote:
| Hmmm.. PAS' trunk PluggableAutheService class already inherits from
| OFS.Cacheable and its _findUser method uses the available cache, so
| it seems like what you want when you say "caching should be applied
| at the 'gateway' into the user folder, where it emits user objects"
| already works. "Thread independence" is a property of
| RAMCacheManager already.
| You do still need to configure the PAS instance to actually do
| caching. But this seems OK. I think you can just ignore caching
| when creating plugins if this is all you want. Even though the
| ZCacheable API sucks, the indirection here is good. I wouldn't want
| PAS itself to have a hard-wired caching implementation in it, and I
| don't mind associating the PAS instance with a cache manager.
Same here. I am fine with the use of ZCacheable. It also can be used
with other cache implementations, for example the
MemcachedCacheManager to share the cache between multiple instances.
Sidnei da Silva
Enfold Systems http://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Zope-PAS mailing list