[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW ISSUE: RMS lacks support for InOrder
|
Title: RMS lacks support for
InOrder Description: InOrder (as
defined) requires two conditions in addition to the use of the
protocol: (a) messages are numbered by RMS in same order they are
submitted ("sent"), (b) messages are delivered by RMD in same
order as they are numbered. There is currently no requirement for (a). Justification: RMD alone
can't enforce InOrder. RMS must do its part. Either it has to be aware of
which DA is required, or the required behavior must be an invariant of RMS
regardless of DA. Target: core Type: design Proposal: Make it an
invariant. Add a sentence at the end of
1st invariant (section 2.3): "During the lifetime of
a Sequence, two invariants are REQUIRED for correctness: The RM Source MUST assign
each message to be delivered reliably a message number (defined below) beginning at
1 and increasing by exactly 1 for each subsequent message to be delivered reliably. These numbers MUST be assigned in the same
order in which messages are sent by the Application Source." |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]