[python-ldap] result_type of connection.result()

[Michael Ströder]

Dave Peticolas wrote:
> Hi, I've noticed (using versions 2.4.19 and 2.4.29) that the result_type tuple
> returned by result() is sometimes RES_SEARCH_ENTRY when all=1 using the default from
> not passing in "all" despite the docstring which seems to say it should always be
> RES_SEARCH_RESULT.

Hmm, I'm not 100 % sure about the SearchResultDone:

https://tools.ietf.org/html/rfc4511#section-4.5.2

> The scenario where this is happening is that multiple asynchronous searches are started
> and then the results are requested for each one by explicitly passing specific msgid
> values for each one, but with all=1.
> 
> Note this doesn't always happen. It seems to be related to the order the results are
> returned from the server.
> 
> Am I just reading the docstring incorrectly?

Could you please provide some example code for testing this?
It might also be relevant which LDAP server you're using.

Ciao, Michael.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3829 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.python.org/pipermail/python-ldap/attachments/20170202/ffe22caf/attachment.bin>