[Issue 10060] libldap: ldap_result return value differs depending on if a search response is already in the response list or not

https://bugs.openldap.org/show_bug.cgi?id=10060

--- Comment #9 from David Härdeman david@hardeman.nu --- Actually, I think changing both cases to return 101 might make more sense.

As shown by Ondřej's PR, ldapsearch already expects that to be the return code (and has done so for a long time).

Further, python-ldap expects 101 to be the return code as well (as do projects using python-ldap, implicitly).

While I understand the appeal of not changing the status quo, not fixing this runs the risk of difficult to reproduce bugs, especially in threaded environments where the return code might differ depending on network delays and the order in which different operations complete (and are processed).