W3C home > Mailing lists > Public > xml-dist-app@w3.org > June 2002

RE: Web-friendly SOAP

From: Eric Newcomer <eric.newcomer@iona.com>
Date: Sun, 16 Jun 2002 12:51:17 -0400
To: "'Jacek Kopecky'" <jacek@systinet.com>
Cc: "'Paul Prescod'" <paul@prescod.net>, "'Mark Baker'" <distobj@acm.org>, <xml-dist-app@w3.org>
Message-ID: <068e01c21556$09133660$6501a8c0@ERIC>

So would this be similar to an earlier proposal, I think from Larry
Masinter, to define SOAP as essentially an equal to HTTP?  Meaning at an
equal layer, with its own protocol type recognized by the Internet?


-----Original Message-----
From: xml-dist-app-request@w3.org [mailto:xml-dist-app-request@w3.org]On
Behalf Of Jacek Kopecky
Sent: Sunday, June 16, 2002 12:35 PM
To: Eric Newcomer
Cc: 'Paul Prescod'; 'Mark Baker'; xml-dist-app@w3.org
Subject: RE: Web-friendly SOAP

 I was suggesting dropping the HTTP binding because HTTP is an
application protocol already supporting metadata and I don't see
a real value of SOAP as the content type in HTTP. If the HTTP
binding stays (which I assume will be the case) and if it is the
secondary binding as I'm suggesting, I wouldn't want any
duplicity of methods and headers, I'd still put headers in only
one place (in an HTTP header or in a SOAP header) and I wouldn't
put the explicit method element in the body.
 The example SOAP envelope in my email is supposed to be sent
over TCP or other similar binding.

                   Jacek Kopecky

                   Senior Architect, Systinet Corporation

On Sun, 16 Jun 2002, Eric Newcomer wrote:

 > If I understand this correctly, you are proposing a kind of dual
 > for example including the method name in the HTTP binding and also within
 > the message itself?
 > My big concern with the move toward HTTP specific binding for SOAP is
 > the ability to easily map to JMS, MQ Series, CORBA, J2EE, etc.  I know
 > Baker says we can do it anyway, and perhaps we can, but to me one of the
 > questions is whether or not we are thinking about just sending the entire
 > message over the transport, and letting the "endpoints" decide what to do
 > with it, and how to interpret it.
 > So you are suggesting including the header information in both the HTTP
 > of the message and also in the SOAP part of the message?
 > Eric
Received on Sunday, 16 June 2002 12:55:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:11:50 UTC