[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: previous results in new search (ITS#404)

The libldap maintains a queue of all responses to requests for a particular
LDAP session. The responses are all associated with the
msgid of their matching request. If you want to prevent ldap_result
from returning the "wrong" responses to a request, you should be
invoking it with the correct msgid in the 2nd parameter to the call.
Also, if you want to throw away the responses for a previous search,
you should use ldap_abandon.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of
> rjakob@duffy1.franken.de
> Sent: Friday, December 17, 1999 11:59 AM
> To: openldap-its@OpenLDAP.org
> Subject: previous results in new search (ITS#404)
> Full_Name: Rolf Jakob
> Version: 1.2
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (
> A call to ldap_result supplies search results from a previous unfinished
> ldap_search
> in case you started an ldap_search before ldap_result returned with
> Clear ? No ?
> Ok, what I did was : I started ldap_search which I know would
> deliver more than
> one result. As I started to write a C++ class for this, I took
> only the first
> result and with the next ldap_search for another pattern w/o
> disconnecting I
> got
> the remaining results from the previous search.
> Now I take all results as this was my intention anyway and it works great.
> I just think with a new ldap_search it should throw away the old results.