- From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Date: Sat, 3 Jul 2004 07:58:56 +0600
- 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. Sanjiva. ----- 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