Re: Unbind and related questions (WG last call on the Java API)

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

At 09:40 PM 3/12/01 -0800, Rob Weltman wrote:
>"Kurt D. Zeilenga" wrote:
>> 
>> Under what circumstances is an API implementation
>> required to send an Unbind request?  with disconnect()?
>> if so, how do you drop the connection without sending
>> an Unbind (such upon receipt of a notice of disconnect
>> or an invalid PDU)?
>
>  An API implementation is not required to send an Unbind request before disconnecting (or otherwise).

Seems this should be made clear in the I-D.

I believe the API should support an mechanism to issue
an Unbind request.

>> How are notices of disconnect handled?
>
>  The client treats the connection as closed by the server (the server is expected to close the connection after sending the notice, but the client treats the connection as closed even if that does not happen)

With regards to the API, does this imply that the API implicitly
calls disconnect or that the application should call disconnect?

>> How are invalid PDUs handled?
>
>  Haven't thought about that (haven't run into it with any servers I've used).

Try connecting to ldap://www.netscape.com:x/ where x is some
port which doesn't speak LDAP.

>How are they handled by the C API?

Good question.  Likely not specified (but should be, IMO).
I believe the best thing to do disconnect and throw an
exception.

>> How are valid but unrecognized by the API PDU handled?
>
>  Do you mean unsolicited messages?

no.

>Or responses to client requests that are valid but not recognized?

yes.

>If the latter, could you give an example of a response to a client request that is valid but not recognized?

A request that would solicit extendedPartialResponses.  The
extendedPartialResponse would not be recognized by the API,
but could be handled by an application (or an extension to
the API) if the API had some means to pass these thru.