MHonArc v2.5.0b2 -->
















ebxml-msg message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: RE: [ebxml-msg] more about MEPs




From: Jacques Durand <JDurand@us.fujitsu.com>
To: "'Jeff Turpin'" <jturpin@cyclonecommerce.com>,       Doug Bunting <Doug.Bunting@sun.com>,       Jacques Durand <JDurand@us.fujitsu.com>
Date: Tue, 21 Sep 2004 17:41:26 -0700






Title: RE: [ebxml-msg] more about MEPs





I would also make case #1 the main driver for this "pull" mode:
something we consider important for our customers, and not just with SMTP.
(the Acknowledgement schemes are indeed limited, which makes precisely the point that
different reliability contracts are needed for "responses")


case #2, ("occasional connectivity" in RosettaNet messaging requirements)
may require something more than an asynchronous pull: that problem seems to be
generally orthogonal to the MEPs being used. I am not even sure how "asynchronous pull" would
work here. What may be needed is, for connections that were interrupted, some way to notify their
sending endpoints that the MSH is available again for receiving. Also, for a sender, some way to figure
that a receiver is down, and behave accordingly.


Jacques