OpenLDAP 2.0.x's libldap_r
michael at stroeder.com
Sun Jul 15 01:19:35 CEST 2001
While we're at it: One thing which might bite other python-ldap
developers as well is that the OpenLDAP libs are not reentrant.
Despite the ugly hack with my wrapper module ldapthreadlock the
problem is still not really solved.
The message from Kurt Zeilenga (attached below) made me curious.
Unfortunately Kurt refused to be more verbose on that. Could anybody
look into this? One idea might be to wrap the lower-level function
calls of libldap_r and write a Python wrapper module above it which
takes care about how libldap_r has to be used.
-------- Original Message --------
Subject: Re: OpenLDAP libs thread-safe?
Date: Fri, 13 Apr 2001 09:57:05 -0700
From: "Kurt D. Zeilenga" <Kurt at OpenLDAP.org>
To: michael at stroeder.com
CC: openldap-software <openldap-software at OpenLDAP.org>
References: <184.108.40.206.0.20010413085505.00a97600 at 127.0.0.1>
At 06:43 PM 4/13/01 +0200, Michael Ströder wrote:
>"Kurt D. Zeilenga" wrote:
>> At 02:42 PM 4/13/01 +0200, Michael Ströder wrote:
>> >The OpenLDAP 1.2.11 libs does not seem to be thread-safe. How about
>> >OpenLDAP 2.0.x libs?
>> While 2.0 provides an experimental -lldap_r. It is not generally
>> thread-safe, but thread-safe if used in a specific manner.
>Can you please elaborate on that?
No easily. Use of -lldap_r really requires one understands
how it is implemented and how its being used. I won't attempt
to generalize the cases where it might be used.
More information about the python-ldap