MHonArc v2.5.2 -->
ebxml-msg message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: Re: [ebxml-msg] RE: [ebxml-dev] Presence of sequenceNumber elementinResponse message.
In reading section 10.1.1 of the 2.0 document, I don't see the confusion.
The first paragraph of that section makes it rather clear the two co-operating
MSH implementations in a conversation are responsible for their own sequence
of SequenceNumber values. I quote:
The SequenceNumber is unique within the ConversationId and
MSH. The From Party MSH 2011
and the To Party MSH each set an independent SequenceNumber as the
Sending MSH within the 2012
ConversationId. It is set to zero on the first message from that MSH
within a conversation and then 2013
incremented by one for each subsequent message sent. 2014
(Sorry for the end of line line numbers caused by Acrobat Reader.)
What's missing?
thanx,
doug
David Fischer wrote:
I think your question is, should SequenceNumber be
incremented at one end or at
both ends?
SequenceNumber should increment in only one (each) direction.
Our intent was to
assure that messages sent from one business partner arrive in the right
order
rather than to sequence an entire conversation, but I don't see this
clearly
spelled out. We may need to add a clarifying statement in the
specification.
Looking at the specification, it appears to be confusing. If SequenceNumber
is
incremented "per conversation" which means in both directions since
a
conversation goes in both directions, there is a problem. Suppose
CompanyA
sends to CompanyB with sequence number 1. Then CompanyA sends
another message
to CompanyB with sequence number 2 at the same time that CompanyB sends
a reply
to CompanyA with sequence number 2. We have two messages with
the same sequence
number. If the sequence is per-conversation, which 2 is correct?
Am I understanding the question correctly?
I am copying the ebXML-Messaging list to solicit other comments.
Regards,
David Fischer
Drummond Group.