- From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
- Date: Tue, 25 Jun 2002 14:09:55 -0700
- To: "Mark Baker" <distobj@acm.org>, "Cutler, Roger (RogerCutler)" <RogerCutler@chevrontexaco.com>
- Cc: <www-ws-arch@w3c.org>
Just to be precise, I think the benefit your are pointing to of HTTP's methods (GET in particular) is that they are universally supported and centrally described as compared to some WSDL document describing operations that may be defined in a decentralized and local manner. I don't think either is in conflict with the Web - central as well as decentral control are both fundamental concepts of the Web architecture. The problem in HTTP is that it is very difficult to go from local to global definition which makes introduction of new features very hard. One of the purposes of SOAP is to bridge the gab between centrally defined features and decentralized features through the use of URIs. This doesn't make the need for universally adopted features go away, however. >You can observe this with any SOAP 1.1 based service. If I come >across some WSDL, where I had no previous knowledge of that service, >then I can't use the service. > >Contrast this with the Web; if I come across a HTTP URI, I know that I >can interact with the resource using HTTP's methods. Henrik
Received on Tuesday, 25 June 2002 17:10:27 UTC