RE: T2 SyncReply and ReliableMessagingMethod in QualityOfServiceI nfo

["Burdett, David" <david.burdett@commerceone.com>]

Arvola

I disagree. You need syncReply in the Via. The attached PDF file titled "Why
you need syncReply in the Via" contains a diagram which illustrates the use
case. Where the first hop is synchronous and the second not.

If we want Via to be used only when intermediaries are being used then you
would need ackRequested held elsewhere, e.g. in the Quality of Service.
However since syncReply can vary from hop to hop (see previous example), you
would then need to also have it in the Via and a rule that the Via
over-rides the QoS. 

There is also the issue that the sender of a message may not know that it is
multiple hop as the PDF file titled "Using ebXML RM behind the firewall"
illustrates. In this case external communications are done synchronously,
but the messaging to an application within the company is done
asynchronously.

I think we need to keep ackRequested and syncReply in the Via, but rename it
... to "Routing Header" perhaps, although I have no strong preference ... ;)

I'd appreciate your thoughts on these use cases.

David
PS Slides very similar to these two were posted ages ago and discussed in
Tokyo last November I think.


-----Original Message-----
From: Arvola Chan [mailto:arvola@tibco.com]
Sent: Wednesday, August 08, 2001 6:59 PM
To: David Fischer; ebXML Msg
Subject: Re: T2 SyncReply and ReliableMessagingMethod in
QualityOfServiceInfo


David:

Sorry for the delayed response. I agree with you that the Via element should
be used exclusively for those cases where intermediaries are involved.
Therefore, it makes sense to move the syncReply and ackRequested attributes
to be under the QualityOfServiceInfo element.

Since there already is a deliverySemantics attribute under the
QualityOfServiceInfo element, and the reliableMessagingMethod attribute can
vary from one hop to another, I think reliableMessagingMethod should stay in
the Via element.

Regards,
-Arvola

-----Original Message-----
From: David Fischer <david@drummondgroup.com>
To: ebXML Msg <ebxml-msg@lists.oasis-open.org>
Date: Monday, August 06, 2001 8:51 PM
Subject: T2 SyncReply and ReliableMessagingMethod in QualityOfServiceInfo


There should be nothing in the Via which is not also in other headers.  Via
should only be used for multi-hop intermediaries.  In the case of SyncReply,
there is no single-hop way of requesting SyncReply=true.

Attributes SyncReply and ReliableMessagingMethod should also be in
QualityOfServiceInfo.  They should retain their current defaults.

Regards,

David Fischer
Drummond Group.


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-msg-request@lists.oasis-open.org


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-msg-request@lists.oasis-open.org

Why you need syncReply in the Via.pdf

Using ebXML RM behind the firewall.pdf