----- Original Message ----- From: "Sudhir" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 2:26 PM Subject: Re: Clients using GET and POST
> hey Steve, > Thanks for the comments. I might have sounded a lil subversive. :). But I > wanted to get things cleared up before I recommend anything to my team. No, > I am not in marketing. I am in Engineering team. > I am aware of the fact that http is one of the transport protocols that can > be used in web services. One can use, ftp, smtp, or whatever. But I was > under the impression that it will be "SOAP over ftp" or "SOAP over HTTP", or > "SOAP over SMTP". Did I get it right?But the GET/POST based services(I am > still not comfortable calling these web services. :)) are purely http based. > Did I miss anything again? > Am I becoming more and more subversive? :) no, you just need to get onto some of the w3c mailing lists to stir things up. GET/POST based services are called, roughly, 'REST' based services. As an example of one, if you install MS SQLXML 3.0 onto a system with SQL Server and IIS, you can send a get request something like http://dbserver/db1?select%20*%20from%20users and get an XML formatted response back. Simple and useful. Now if you start doing SOAP over SMTP, or SOAP over SS7, is it still a web service? These are religious issues that will only be resolved over time, if ever. My view is that regardless of the name, it is all about loosely couple distributed systems. Marshalling layers are only relevant for interoperability, HTTP is used today as it goes through firewalls, but to build a high availability global distributed system, you need to use a reliable async messaging system. ' See : http://www.iseran.com/Steve/papers/when_web_services_go_bad.html for details on what happens when you dont
