Regarding this statement,
MQSeries provides an application-level api that can be
used to send a DR, but it is optional. That doesn't make MQSeries any
less reliable. MQSeries nodes only concern themselves with ensuring that
the
message is safely persisted in the adjacent node/queue.
Let's be careful. IBM MQSeries is a proprietary protocol and
implementation that assumes, at least for the purposes of reliable
messaging, that all nodes on the path have it. That enables it to
guarantee exactlyOnce delivery with a minumum of fuss.
ebXML does not have the luxury of that assumption. We can't make any
assumptions on the implementations of any of the nodes. We have to make
crystal clear what are the responsibilities of intermediate nodes to assure
that reliable delivery goes all the way down the path. Some assurance that
the message got there helps considerably for this open system.
Regards,
Marty
*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown
Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
christopher ferris <>@Sun.COM on 09/07/2001
04:55:26 PM
Sent by:
To:
"ebXML Messaging (E-mail)" <>
cc:
Subject: RE: T2 PLEAE READ - Suggested solution to RM Issues
Phew this thread is getting long;-)
Amazingly enough, DB agrees with me on a majority of
my points... Someone please check for pods in David's
office!!!
More comments below. I won't <snip/> as this is a valuable
artifact for the resolution of these issues.
My comments with <cf1/> this go.
Cheers,
Chris
-----------------------------------------------------
Chris
Changea 4 & 5 suggest "Make the return of a Delivery Receipt required if
deliverySemantics=OnceAndOnlyOnce"
Arvola and David F agree with this whereas Chris Ferris disagrees. I can
see
benefits in both approaches. So I think we should talk about this on next
Monday's conference call.
See other comments below marked with <db1></db1> to distinguish from
earlier
comments.
David
