[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-rx] i066:Proposal to remove LastMessage, but retain LastMessage functionality
Bob: In a LastMessage-less scenario, If RMS got
all the acks it was waiting for (having knowledge of what was last message it
sent for this sequence) it has no need to close the sequence: it can
terminate it directly. Bottom line is: "someone"
(either RMS or RMD) will have to wait for all messages to have been received
(or wait for a confirmation of this) to take action for reclaiming resources on
RMD side. - With LastMessage, RMD has to remember. - Without LastMessage, RMS has to
remember. Sure there is a final additional TerminateSequence
to be sent in second case, but that small overhead is to balance with the
increased complexity of the protocol in first case. Note that this overhead in the sequence
termination protocol disappears in case the AS happens to knows it was its last
message - or cares to signal this to RMS - only *after*
having sent it, (as opposed to at the time that last message is being sent)
which I expect to be by far the most common case. Indeed in that case, an empty
additional message with LM will have to be sent. Jacques From: Doug Davis
[mailto:dug@us.ibm.com]
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]