Lists Home |
Date Index |
- To: "Jens Jakob Andersen, PDI" <firstname.lastname@example.org>,"xml-dev" <email@example.com>
- Subject: RE: RE: [xml-dev] Will Web Services Kill HTTP?
- From: "Dare Obasanjo" <firstname.lastname@example.org>
- Date: Sun, 14 Apr 2002 13:22:23 -0700
- Thread-index: AcHjA+56l6Aj8+xHSlK2c+m6NPaI3gApG4OAABHq7uA=
- Thread-topic: RE: [xml-dev] Will Web Services Kill HTTP?
> -----Original Message-----
> From: Jens Jakob Andersen, PDI [mailto:email@example.com]
> Sent: Sunday, April 14, 2002 4:36 AM
> To: xml-dev
> Subject: SV: RE: [xml-dev] Will Web Services Kill HTTP?
> Web-services will allways need HTTP as the transport layer
> protocol -ø just as well as HTTP will allways need TCP/IP etc.
Besides the fact that the phrase "web services" contains the word "web" I don't see anything that implies that web services require HTTP in any way, shape or form.
From what I've seen of web services there are mainly RPC calls that use XML as the data transfer format. Even though toolkits such as VS.NET produce a user friendly page for people to try out a page[0,1] in general people aren't expected to browse to a web service and interact with it. Thus the primary protocol could be NNTP, SMTP, or FTP (all severely abused) behind the seens and most web service applications wouldn't be able to tell much of the difference.
Please enlighten me as to why you think web services *need* HTTP.
PITHY WORDS OF WISDOM
Computers are not intelligent. They only think they are.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights reserved.