https://bugs.openldap.org/show_bug.cgi?id=8871
--- Comment #7 from Ondřej Kuzník <[email protected]> --- On Mon, Mar 08, 2021 at 12:30:55PM +0000, [email protected] wrote: > --- Comment #6 from [email protected] <[email protected]> --- > It seems cancel is not very useful if one cannot cancel itself and other > thread > can not cancel over same connection until the thread which performs the > cancelled operation timeout either during the operation itself or during > ldap_result, or doing the polling while waiting for ldap_result. Once you > have > timed out, there is no need to cancel, isn't it? This bug tracker is not for usage questions, these should be posted to the appropriate mailing list, usually openldap-technical. None of what you're asking for would have worked if the thread calling ldap_result were to release its locks anyway. You can still send a cancel exop and you will get a response to both, if you require that the other thread be notified immediately, you need to do that in your own application as libldap has never had such ambitions. -- You are receiving this mail because: You are on the CC list for the issue.
