- From: Mark Baker <distobj@acm.org>
- Date: Tue, 26 Mar 2002 08:26:05 -0500 (EST)
- To: henrikn@microsoft.com (Henrik Frystyk Nielsen)
- Cc: tbray@textuality.com (Tim Bray), www-tag@w3.org
> In short, HTTP can break HTTP, SOAP can break SOAP, and SOAP can break > HTTP if combined in certain ways, but we already know that, right? Most definitely. You know I agree 100%. But the issue is *common practice* and *expectations* on the part of developers. The vast majority of them, when sitting down to code with SOAP, will break HTTP, because their expectations are that SOAP is an RPC protocol. On the other hand, the majority (probably not "vast" though 8-) of those sitting down to code with HTTP, will not break HTTP. I don't believe one can successfully evaluate the chances of success of a particular technology without considering how people are using it. That's why I don't personally expect SOAP to see much success. But that in no way prevents me from attempting to make it the best protocol it can be. 8-) MB -- Mark Baker, Chief Science Officer, Planetfred, Inc. Ottawa, Ontario, CANADA. mbaker@planetfred.com http://www.markbaker.ca http://www.planetfred.com
Received on Tuesday, 26 March 2002 08:20:55 UTC