[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: MAJOR TECNICAL comments on v0.98
Mr. Christopher Ferris, On Fri, 09 Mar 2001 14:03:03 -0500 christopher ferris <chris.ferris@east.sun.com> wrote: ... > MAJOR TECHNICAL > > section 8.5.8 > > 1 - line 574 - Requiring that SequenceNumber ONLY be present with > OnceAndOnlyOnce and Guaranteed seems to me to be a limitation > that could constrain an implementation from using SequenceNumber > as a means of enforcing RM when the SequenceNumber is > applied by the MSH and NOT by the Application (From Party). > > I would much prefer that SequenceNumber ONLY be present > when OnceAndOnlyOnce is specified, and that the semantics > of messageOrderSemantics MAY be used to instruct the receiving > MSH to deliver the messages in the order in which the Application > determines by virtue of the SequenceNumber. I'm not sure if I understand your suggestion correctly. Do you mean following? - When BestEffort is specified, SequenceNumber is never present - When OnceAndOnlyOnce is specified, SequenceNumber is *always* present, even if messageOrderSemantics is not specified If so, I agree to this change. Regards, -- SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com> TEL:+81-45-476-4590(ext.7128-4241) FAX:+81-45-476-4726(ext.7128-6783) Planning Dep., Strategic Planning Div., Software Group, FUJITSU LIMITED
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC