W3C home > Mailing lists > Public > www-ws-arch@w3.org > May 2002

RE: SOAP and transfer/transport protocols

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Tue, 28 May 2002 08:07:45 -0400
Message-ID: <9A4FC925410C024792B85198DF1E97E40339AF34@usmsg03.sagus.com>
To: www-ws-arch@w3.org


> -----Original Message-----
> From: Mark Baker [mailto:distobj@acm.org]
> Sent: Tuesday, May 28, 2002 7:41 AM
> To: Champion, Mike
> Cc: www-ws-arch@w3.org
> Subject: Re: SOAP and transfer/transport protocols

> It is a complete non-starter for an Internet scale architecture to do
> what you and David are suggesting. 

Perhaps because our employers sell millions of dollars worth of software to
companies that do the kinds of things that we are suggesting, and have been
doing it for years and years!  Suggesting to them that they rip out their
DCOM, CORBA, J2EE, MQ, etc. systems and put in HTTP Everywhere would be the
non-starter, I'm afraid.

> On the other hand, if you 
> only want Web services to work behind the firewall, then this would be 
> the easiest way to ensure that

Fair enough ... a lot of this kind of stuff *is* done behind firewalls, and
many of the issues you raise *do* become salient when moving to the Web.
Nevertheless "web services" are quite appropriate to application integration
and supply chain integration problems that don't have to deal with "pesky
trust boundaries."  That challenge is to do it better, in a cheaper, more
standardized way.  That's probably why our employers pay us be here, so
forgive us for reminding you of our requirements :~)
Received on Tuesday, 28 May 2002 08:07:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:00 GMT