caching

[Jerome Alet]

On Wed, Apr 20, 2005 at 07:17:39PM +0200, Michael Ströder wrote:
> 
> Note that the caching in OpenLDAP client libs was considered broken.
> That's why the wrapper code for making OpenLDAP's client-side caching
> available to python-ldap was removed.

I thought about python-ldap specific code, by modifying the 
search methods and invalidating modified entries in the 
add/modify/delete methods

> > if yes, I'm ok to try to do it.
> 
> I'd go for sub-classing LDAPObject and hook into method search_ext_s().

Just what I thought at first glance.

> Issues which come to mind:
> * There can be lots of subtle details to consider which might lead to
> different search results (e.g. access control, the ManageDSAIT controls,
> etc.)
> * take care of flushing the right objects from your cache when modifying
> entries
> * for security reasons flush your whole cache when (re-)binding on a
> given LDAP connection
> 
> I'm sure there are more issues...

Well, if I've got the time, I'll give it a try next week.

bye

Jerome Alet