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

RE: SOAP and the Web architecture

From: Larry Masinter <LMM@acm.org>
Date: Tue, 28 Aug 2001 22:52:44 -0700
To: "David Orchard" <orchard@pacificspirit.com>
Cc: <xml-dist-app@w3.org>
Message-ID: <NDBBKEBDLFENBJCGFOIJAEKKFIAA.LMM@acm.org>
# What do you mean by "support" and "requires something"?  If SOAP requires
# that some, maybe even all software, change 1 parameter, does that count as
# "not supported"?

Yes. Otherwise it would be trivial to change SOAP to use another
port (or, for that matter, another protocol). Almost all firewall
software can easily be configured to change the 1 parameter to
"allow outbound TCP connections on port 5049".

And then there would be no reason to use HTTP because it
"goes through firewalls". However, it's frequently been asserted
that the main reason for SOAP to continue to use port 80 is because
of the impossibility of getting system administrators to change
this one parameter which is clearly within their control to support.

If the plan is to work with existing deployed HTTP proxy infrastructure
to ease the SOAP deployment scenario, then it isn't possible to
wish away the negative interactions with the actual characterstics
of that infrastructure (such as limits on the length of URLs).

If this isn't the plan, then the justification for using HTTP at
all has been weakened significantly.

You can't have it both ways.

Larry
Received on Wednesday, 29 August 2001 01:53:29 GMT

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