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] Interaction between AckRequested,DuplicateElimination,and SyncReply elements
Hmmm,
That wasn't my reading of 2.0 rev C. If others agree it's a possible reading of
the text, it should be fixed. I agree with Arvola that duplicate elimination
and returning a copy of the first response should be triggered by the
DuplicateElimination element. AckRequested should simply determine whether or
not that first response includes an Acknowledgment element.
Were others confused? What change would improve the wording?
thanx,
doug
Arvola Chan wrote:
> Doug:
>
> In earlier versions of the spec when we had only the concept of Reliable
> Messaging and not separate control of AckRequested and DuplicateElimination,
> it was clear that whenever a receiver receives a reliably delivered message
> that is not a duplicate, it is obligated to at least make a persistent copy
> of the message ID as well as a persitent copy of the first response message.
> When a received reliably delivered message is determined to be a duplicate,
> the receiver is supposed to return the saved first response message.
>
> Now that AckRequested and DuplicateElimination can be controlled separately,
> it is not clear whether the behavior to save the first response message and
> to return the saved first response message in reply to a duplicate message
> is triggered by the AckRequested element or by the DuplicateElimination
> element.
>
> I would have preferred that the above behavior be triggered by the
> DuplicateElimination element. However, Version 2.0 rev C indicates that the
> above behavior should only be exhibited by the receiver MSH if the
> AckRequested element is present.
>
> Regards,
> -Arvola
>
>