Re: Protocol: Unbind

[Hallvard B Furuseth <h.b.furuseth@usit.uio.no>]

Sorry, previous message got truncated.  I'm trying again.
The message is the same until the '----------------' line.

Jim Sermersheim writes:
>>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 12/10/03 4:36:13 AM
>>>>
>>> 4.3. Unbind Operation 
>>
>>> Any outstanding operations 
>>> on the server are, when possible, abandoned, and when not possible,
>>> completed without transmission of the response. 
>>
>>Should probably have a separate section which says the same happens if
>>the connection is lost (e.g. if the client abruptly closes the
>>connection).
> 
> Hmm, I'm thinking these instructions don't offer any benefit. We
> already said that the protocol peers cease to transmit. I propose
> removing this language.

I agreed at first, but on second thought there is nowhere else which
says that abandoning outstanding operations is preferred over completing
them.

BTW, if you move or remove this language, I believe you should also
remove the language in section 4.4.1 (Notice of Disconnection) which
says 'the server MUST follow the procedures of Section 4.3.'  I expect
it's the above procedure which this text refers to.

----------------

Section 4.4.1 (Notice of Disconnection) goes on to say:

>   As with a connection close due to network failure, the
>   client MUST NOT assume that any outstanding requests which modified
>   the Directory have succeeded or failed.

This is not stated elsewhere.  It should be stated in a section about
connection close/network failure/unbind in general, not in section
4.4.1.

However, it is incomplete.  The client also MUST NOT assume that the
server attempted to perform the request at all.  Maybe this could all be
joined with the text about not knowing the result of abandoned
operations:  "A client MUST NOT assume that a request to which it has
received no response (e.g. because it was abandoned or the connection
was lost), has been performed, nor that it has not been performed."

-- 
Hallvard