-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Even though I am the perpetrator, I think the current way of caching,
using ZCacheable and RAM cache managers, is absolutely horrific. It's
cumbersome to set up and the ZCacheable API is ugly as sin using it
from code. I think simplification is
On Jul 29, 2006, at 10:28 AM, Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Even though I am the perpetrator, I think the current way of
caching, using ZCacheable and RAM cache managers, is absolutely
horrific. It's cumbersome to set up and the ZCacheable API is ugly
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29 Jul 2006, at 11:44, Sidnei da Silva wrote:
| 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
|
According to Chris McDonough:
> On Jul 29, 2006, at 10:28 AM, Jens Vagelpohl wrote:
> > I personally don't see any need to have caching in plugins
> > themselves. Instead, caching should be applied at the "gateway"
> > into the user folder, where it emits user objects. These user
> > objects
