Re: mo timeout on ldap_result call in ldap_sasl_bind_s

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

At 12:37 AM 9/12/2004, HagaiY@Cyber-Ark.com wrote:
>        I am using the OpenLDAP API version 2.1.22 to get data from windows Active Directory, I am binding to the server using sasl, I am using the LDAP_OPT_NETWORK_TIMEOUT option to set a timeout to network actions. Despite that I see that the ldap_sasl_bind_s function calls the ldap_result function with NULL for the timeout parameter, this leads to a call to the select function with NULL as the timeout parameter, can't this cause my thread to wait forever ? 
>
>prior to the ldap_result call a connect is being made to the server (with the ldap_pvt_connect function), in this function after a non-blocking connect there is a select that uses the Timeout that I have used for the LDAP_OPT_NETWORK_TIMEOUT option, why in the connect there is a timeout and later no ? 

Because that's the extent of LDAP_OPT_NETWORK_TIMEOUT
applicability.  LDAP response timeouts are intended to be
set by yet unimplemented LDAP_OPT_TIMEOUT.  Generally,
applications needing response timeouts should use the
async API.

Kurt