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

RE: SOAP and the Web architecture

From: David Orchard <orchard@pacificspirit.com>
Date: Tue, 28 Aug 2001 14:44:03 -0700
Message-ID: <01C12FCF.E28FDFA0.orchard@pacificspirit.com>
To: "xml-dist-app@w3.org" <xml-dist-app@w3.org>
Mark,

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"?  It seems to me that if SOAP requires a configuration 
change, then the software supports it and requires no software change. 
 Certainly a separate download and install isn't required.  I separate and 
distinguish between code changes and on-site configuration changes, and I'm 
wondering what you and others think.

Do you classify configuration changes under "suddenly requires" or 
"support"?

Thanks,
Dave

On Tuesday, August 28, 2001 1:38 PM, Mark Nottingham [SMTP:mnot@mnot.net] 
wrote:
>
> > If an arbitrary limitation of the software gets in the way of 
meaningful
> > useful real-world uses then it is lacking a feature whether we call it
> > broken or not.
>
> I don't think it's arbitrary; implementations need to protect
> themselves from overflow attacks, etc. Of course, if the world
> decides that longer URIs are a good and useful thing, fine. However,
> one of the ideas behind having HTTP bindings for SOAP is that it will
> be able to use the existing infrastructure (re-use existant HTTP
> stacks, and use HTTP for routing out of the firewall). If SOAP
> suddenly requires something that a good part of that infrastructure
> doesn't support, we lose a lot of value.
>
>

<snip/>
>
> Cheers,
>
>
> --
> Mark Nottingham
> http://www.mnot.net/
>  
Received on Tuesday, 28 August 2001 17:44:10 GMT

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