OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: New Issue; SequenceAcknowledgement:Final assumption of deliverability

Modify definition of SequenceAcknowledgement:Final to reflect accurate ending delivery capability status.

The protocol defines the SequenceAcknowledgement:Final element which contains the final summary of message acknowledgements at the closure of a sequence. It is assumed that the RMD has taken responsibility for all messages that have been acknowledged.  Depending upon the operation of the RMD and its interface with the application, Messages that have been previously acknowledged as received by the RMD, may never be deliverable.  One such case of note that comes to mind is the situation of a message sequence that is being delivered in-order to an application which is closed at the time when one or more gaps that may exist in the sequence.  If this situation occurs, the RMS will have incorrect information concerning exactly which messages have been or will be deliverable at the conclusion of a sequence.

Note that there is nothing in the spec that states what the RMS is to do with the information contained in SequenceAcknowledgement:Final.  This proposal does not add any such statement, but it does permit the information to be potentially interpretable.

Target: core

Reference Core Spec CD03
insert after line 613:
SequenceAcknowledgemnt:Final shall identify only those messages that have been delivered or which the RMD has taken responsibility for delivery without regard to the previous acknowledgement status of any message.

State Table impact: None


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]