- From: Eric Newcomer <eric.newcomer@iona.com>
- Date: Thu, 7 Dec 2000 13:32:15 -0500
- To: "David E. Cleary" <davec@progress.com>, "Michael Champion" <mchamp@mediaone.net>, <xml-dist-app@w3.org>
We have the same view and would prefer convergence of the two efforts, if possible... -----Original Message----- From: xml-dist-app-request@w3.org [mailto:xml-dist-app-request@w3.org]On Behalf Of David E. Cleary Sent: Thursday, December 07, 2000 11:02 AM To: Michael Champion; xml-dist-app@w3.org Subject: RE: SOAP and ebXML > I'm wondering if participants here agree with the notion that SOAP is for > simple services and ebXML for mission critical transactions. If so, what > about ebXML makes it more suitable for mission critical work? > (Transaction > processing support, maybe?) I agree with the notion that ebXML is not appropriate for every uses case, and that SOAP is a better choice for many applications. What I do not agree with is that SOAP can not be the base upon which something such as ebXML could be built. A perfect example of this is BizTalk. It has the same requirements as ebXML, but is built on top of SOAP. So, in conclusion, my point is that XP can be used for mission critical work if you build the required services on top of it. David Cleary Progress Software
Received on Thursday, 7 December 2000 13:32:35 UTC