W3C home > Mailing lists > Public > www-ws-arch@w3.org > July 2004

Re: Requesting WSDL Files

From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Date: Sat, 3 Jul 2004 07:58:56 +0600
Message-ID: <085b01c460b7$1a140da0$84614109@LANKABOOK>
To: <jsled@asynchronous.org>, "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>
Cc: "Anne Thomas Manes" <anne@manes.net>, <www-ws-arch@w3.org>

Check the SOAP spec and see .. its not done in a protocol independent
manner; its part of the SOAP/HTTP binding only.

That is, if you're using HTTP to carry the SOAP message *and* the
semantics of the underlying interaction are "safe" (per what HTTP GET
defines) and if the data is of simple types then you can use HTTP GET.

Absolutely nothing wrong with that.


----- Original Message ----- 
From: "Josh Sled" <jsled@asynchronous.org>
To: "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>
Cc: "Anne Thomas Manes" <anne@manes.net>; <www-ws-arch@w3.org>
Sent: Saturday, July 03, 2004 12:42 AM
Subject: RE: Requesting WSDL Files

> On Fri, 2004-07-02 at 14:32, Savas Parastatidis wrote:
> > I think thatís the wrong thing to do since itís transport
> > protocol-specific. Oh wellÖ itís there now, so nothing to do about it!
> Indeed.  Why even use HTTP, at that point?
> Why not just develop a new application protocol on top of TCP?
> ...jsled
Received on Saturday, 3 July 2004 00:35:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:11 UTC