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

Re: Please assist - LDAP client library: ldap_modify usage

To: Alex Xia <axia@terayon.com>
Subject: Re: Please assist - LDAP client library: ldap_modify usage
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Wed, 01 Mar 2000 11:20:52 -0800
Cc: openldap-software@OpenLDAP.org, Alex Xia <axia@terayon.com>, Sasha Fertelmeister <sasha@terayon.com>
In-reply-to: <38BB7B3D.F251EA3E@terayon.com>
References: <Pine.SGI.3.95.1000228170410.137H-100000@bleu.west.spy.net>

At 11:54 PM 2/28/00 -0800, Alex Xia wrote:
>I am building a LDAP client and is using the ldap_modify api call.
>I want to do the modify asynchrously, using ldap_modify() and
>ldap_result().  I also want to keep track of which ldap modify
>succeeded and which did not.  Since the results can come back
>out of order, I don't want to wait for a particular message in the
>ldap_result() function, instead I pass LDAP_RES_ANY in the
>function call.  Hopefully the process is more efficient this way
>since faster responses is processes first.  But how can I keep track
>of which ldap modify successed?  The ldap_result() call doesn't
>seem to give me back the message id of the modify.

LDAP returns LDAPMessage structures which contain the message
identifier.

	Kurt

Prev by Date: Re: Fatest way to transfer ldap data to another machine
Next by Date: Client
Index(es):
- Chronological
- Thread