Jacques Durand wrote:
> Tom and all:
>
> Overall I do agree with Scott's position, as he stated below.
>
> But my issue was different (see second part of my email 9/8):
>
> Since you ask me, here it is.
> (BTW, I know I should have had this discussion at f-2-f .
> But I think we went too quickly on this "new" issue anyway, not even
> formally registered,
> almost closed as soon as it was raised, and I admit I missed it for
> whatever reason.
> I like to have time to read things.)
>
I actually think that we might have moved too fast on resolving Sunil's
overnight issue. However, it takes a 2/3 majority to overturn a
previous motion (this is different than motion to reconsider).
Thus, I would prefer that we have an email discussion on Jacque's and
Scott's points, and we
wait for general agreement on a change to make (if we get agreeent)
before we open a new issue to overturn a prior motion resolution, we
I copy text from the minutes at the f2f:
"
The text is currently unclear on whether sequenceNO other than 0 can be
used without ordering. The general consensus is no.
Without ordered deliver, the groupID is unique for each sent message.
Thus the group size is considered to be one in this case.
"
The rest of the decsions we made were based on the above "general
consensus" which,
I must admit, we never made a motion on.
"
Agreement to replace RefToMessageID with two new elements:
* RefToGroupID
* RefToSequenceNo
Agreement to replace RefToMessageID with two new elements:
* RefToGroupID
* RefToSequenceNo
Four alternative proposals:
1)
As Sunil suggested above: Move sequenceNo sub element from Message
header to Request:MessageOrder sub element.
2)
· Un ordered messages use seq no = 0 always, in Message header
(for use in Response/RefToSequenceNo), and messageOrder subelement is
not present in Request header
· Ordered messages use seq no >=1 in Message header, and the
messageOrder subelement is present in Request header element.
3)
· Un ordered message does not have seq no present in Message
header (no RefToSequenceNo element present in Response header), and the
messageOrder subelement is not present in Request header element.
· Ordered messages use seq no >= 0 in Message header, and the
messageOrder subelement is present in Request header element.
4)
same as 3, except move messageOrder status attribute to be attribute of
sequence number element, and remove messageOrder element.
Meeting consensus on alternative 4) above.
"
Tom Rutt
WSRM Chair
Fujitsu
--
----------------------------------------------------
Tom Rutt email: ;
Tel: +1 732 801 5744 Fax: +1 732 774 5133
