W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2001

RE: [Fwd: Business Case for using SOAP]

From: Nilo Mitra (EMX) <Nilo.Mitra@am1.ericsson.se>
Date: Thu, 6 Dec 2001 16:50:44 -0600
Message-ID: <C358DED30DFED41192E100508BB392278C3A87@eamrcnt716.exu.ericsson.se>
To: "'Marwan Sabbouh'" <ms@mitre.org>, Christopher Ferris <chris.ferris@sun.com>
Cc: xml-dist-app@w3.org
The area where I think we need further motivation is: why use SOAP as an envelope rather than define
one's own XML vocabulary, as many industry groups have done. One cart-before-the-horse reason might be:
to expose them as web services.
Nilo

> -----Original Message-----
> From: Marwan Sabbouh [mailto:ms@mitre.org]
> Sent: Thursday, December 06, 2001 8:59 AM
> To: Christopher Ferris
> Cc: xml-dist-app@w3.org
> Subject: Re: [Fwd: Business Case for using SOAP]
> 
> 
> >>I would cite the extensibility framework and processing
> >>>model for starters.
> 
> 
> Agreed.
> 
> Marwan
> 
> 
> 
> Christopher Ferris wrote:
> 
> > Marwan,
> >
> > These are all advantages of XML in general, not necessarily
> > of SOAP. I think that what needs to be described are
> > the things that make the case for SOAP as being a better
> > solution than just XML.
> >
> > I would cite the extensibility framework and processing
> > model for starters.
> >
> > Cheers,
> >
> > Chris
> >
> > Marwan Sabbouh wrote:
> >
> > >
> > > 
> --------------------------------------------------------------
> ----------
> > >
> > > Subject:
> > >
> > > Business Case for using SOAP
> > > From:
> > >
> > > "Roger L. Costello" <costello@mitre.org>
> > > Date:
> > >
> > > Tue, 04 Dec 2001 11:01:25 -0500
> > > To:
> > >
> > > soap-user@xml.apache.org
> > >
> > >
> > > Hi Folks,
> > >
> > > I need to put together a business case for using SOAP.  I 
> would like to
> > > collectively come up with a list of advantages to using SOAP.
> > >
> > > Advantages:
> > >
> > > 1. Easy editing and debugging: SOAP messages are XML 
> documents. They can
> > > be created and edited using a simple text editor.  
> Consequently, they
> > > are easier to read and debug than binary protocols.
> > >
> > > 2. XML family of tools available: Since a SOAP document is an XML
> > > document you have all the XML tools available for 
> processing the SOAP
> > > document, e.g., XSLT for transforming.
> > >
> > > 3. Separation of concerns: SOAP is independent of how it is to be
> > > transported.  Thus, SOAP can be transported using HTTP, SMTP, etc.
> > >
> > > 4. Language/platform independent: SOAP (XML) is language 
> and platform
> > > neutral.  Consequently, it is usable in a variety of environments.
> > >
> > > 5.  What else?
> > >
> > > I read this in a book recently: "Saying that SOAP 
> replaces CORBA or DCOM
> > > is an oversimplification.  SOAP is missing most of the 
> features that
> > > developers expect form a robust distributed object 
> protocol, such as
> > > grabage collection or object pooling."  Question: If SOAP does not
> > > replace CORBA/DCOM/RMI then what is SOAP's role?  /Roger
> > >
> > >
> 
> 
Received on Thursday, 6 December 2001 17:51:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 22:28:13 UTC