W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2002

RE: Article: Fat protocols slow Web services

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Thu, 10 Jan 2002 12:42:55 -0500
Message-ID: <9A4FC925410C024792B85198DF1E97E4022E3E23@usmsg03.sagus.com>
To: xml-dist-app@w3.org


>
> Frank D. Greco wrote:
> 
> 
> The primary benefit of SOAP is *across* the firewall.  I 
> sincerely  doubt you'd convince the major global investment banks that
SOAP is
> superior to what they already have for *internal* applications.
> Maybe in a few years when SOAP (et al) frameworks are available,
> but not now.

I wouldn't quarrel with this, nor pretend to understand the needs of major
global investment banks. But I'd suggest that SOAP is all about leveraging
the web infrastructure and expertise that is already in place, be it inside
or outside the firewall. Even internal application integration projects
could in principle benefit from SOAP et al. (even without the frameworks and
wizards) when there is a good synergy between the XML aspect or the HTTP
aspect of SOAP and the application in question.  For example, using SOAP
rather than CORBA could leverage other EAI tools that import/export data in
XML or products that implement their own SOAP interfaces.  Likewise, if an
enterprise has invested heaviliy in an intranet infrastructure with
industrial strength VPNs, firewalls, authentication, etc. designed with HTTP
and HTML web applications in mind, SOAP should be able to leverage it more
directly than CORBA could.  

Of course, an enterprise with a strong, working CORBA (or COM)
infrastructure and experience base should probably keep on using that for
internal work.
Received on Thursday, 10 January 2002 12:43:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:05 GMT