Hi Michael,
Thanks for your response. I'll play around with it. The sleep time added
was to enable us to test the behavior of result. We are calling python
through Smalltalk and we add the sleep on our end (the calling thread in
Smalltalk not python) to enable other threads to process while wai
Olivier,
please follow-up on the python-ldap-dev (Cc:-ed) list because this is
certainly of general interest.
Olivier Sessink wrote:
> 2008/4/23 Michael Ströder <[EMAIL PROTECTED]>:
>> Hmm, I'm not sure I would consider this to be very high-level. If a
>> higher-level API is ever add to python-
Ron Teitelbaum wrote:
While polling it appears that we have to call result for every record that
is waiting to be read. Since we added a 250 millisecond delay between calls
larger queries are taking a really long time.
Why do you wait such a long time in an extra time.sleep() call?
re
Olivier,
Olivier Sessink wrote:
>
> In my use of python-ldap I've often used a self-developed high level
> class for ldap-object handling.
>
> Adding a new ldap entry for example (ld is a python-ldap object):
>
> lo = LdapOO.LdapObject()
> lo.set_dn_attribs(['cn'])
> lo.add_attribute_value('cn
