Doug,
This seems wordier than necessary. The text added for DiscardEntireSequence
does not use the definition you added for discard at all. The other two values
seem like they would benefit from simply changing the word discard to not
deliver.
I don’t think it is necessary to prepend “note” to the sentence added
below or “quote” any of the words in this proposal.
From: Doug Davis
[mailto:dug@us.ibm.com]
Sent: Thursday, June 08, 2006 12:03 PM
To: ws-rx@lists.oasis-open.org
Subject: [ws-rx] [NEW ISSUE] Define "discard"
Title: Define "discard"
Description/Justification:
In WD13.pdf section 3 - line 308++ - should
we define "discard" - its not
clear to me that we mean the discarded
messages will NEVER (and have
never) be delivered to the AD, instead of
just "from now on the RMD
won't deliver them".
Target: wsrm spec
Type: design
Proposal:
Modify the text for
IncompleteSequenceBehavior to be (new stuff in bold):
(Chris/Bob is this new stuff consistent with
what you guys wanted?)
/wsrm:CreateSequenceResponse/wsrm:IncompleteSequenceBehavior
This optional element, if present, specifies
the behavior that the RM Destination will exhibit upon the
closure of an incomplete sequence. For
the purposes of defining the values used, the term
'discard' refers to the RM Destination
never delivering a particular message to the AD.
A value of “DiscardEntireSequence” indicates
that the entire sequence will be discarded by the RM
Destination if the sequence is closed when
there are one or more gaps in the
SequenceAcknowledgement/Final. Note, this
means that the RM Destination will not deliver any
messages to the AD until the final
SequenceAcknowledgement is determined and there are no
gaps in it.
A value of “DiscardFollowingFirstGap”
indicates that messages in the sequence beyond the first gap will
be discarded by the RM Destination when
there are one or more gaps in the
SequenceAcknowledgement/Final.
The default value of “NoDiscard” indicates
that no acknowledged messages in the sequence will be
discarded by the RM Destination.