Re: How does one handle the LDAPMessage if the return isLDAP_RES_SEARCH_RESULT?

[Ken Witzke <kwitzke@apple.com>]

Thanks.  

I had been using the UMich baseline whose client tools were not as complete.
Also the UMich mailing list produced no response to my question.

 On 12/17/01 11:21 AM, "Howard Chu" <hyc@highlandsun.com> wrote:

> I'd say the code in OpenLDAP clients/tools/ldapsearch.c gives a pretty good
> example of what to do.
> 
> -- Howard Chu
> Chief Architect, Symas Corp.       Director, Highland Sun
> http://www.symas.com               http://highlandsun.com/hyc
> Symas: Premier OpenSource Development and Support
> 
>> -----Original Message-----
>> From: owner-openldap-software@OpenLDAP.org
>> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Ken Witzke
>> Sent: Monday, December 17, 2001 10:47 AM
>> To: openldap-software@OpenLDAP.org
>> Subject: How does one handle the LDAPMessage if the return
>> isLDAP_RES_SEARCH_RESULT?
>> 
>> 
>> Folks,
>> 
>> I have, I hope, been finally directed to the correct list to ask the
>> following question.
>> 
>> I have always easily dealt with the LDAPMessage if the ldap return code is
>> LDAP_RES_SEARCH_ENTRY from an LDAP search.
>> 
>> The example search code that I have also only deals with
>> LDAP_RES_SEARCH_ENTRY.
>> 
>> However, I would like to be able to deal with the LDAP_RES_SEARCH_RESULT
>> return code which seems to indicate " an entire chain of entries
>> matching a
>> previously initiated search request, along with a final outcome".
>> 
>> Does anyone have any available sample code that processes the
>> LDAPMessage in
>> this case?
>> 
>> Thanks.
>> 
>> -Ken
>> 
> 
>