Re: T2 SyncReply and ReliableMessagingMethod in QualityOfServiceInfo

[Arvola Chan <arvola@tibco.com>]

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