W3C home > Mailing lists > Public > xmlp-comments@w3.org > June 2001

RE: [soapbuilders] XML Protocol: Proposals to address SOAPAction header

From: graham glass <graham-glass@mindspring.com>
Date: Thu, 7 Jun 2001 17:22:15 -0400 (EDT)
To: <soapbuilders@yahoogroups.com>, <xmlp-comments@w3.org>
Message-ID: <NDBBKIMDGDFEBNNMEMMNCEIDDMAA.graham-glass@mindspring.com>
hi martin,

i vote for (B). 

i doubt that anyone will ever use SOAPAction for filtering, 
as the original intent seemed to be, and i think there would be 
too much variation on what "standard" WSDL files contain
for any system to be handle the variations in a useful way.

i'd rather see XMLP be a simplification of the current SOAP
specification rather than have all these straggling issues
as hangers-on.

also, maybe the content-type should be "soap" instead of "text/xml"?

cheers,

graham glass,
chief architect
the mind electric

http://www.themindelectric.com

-----Original Message-----
From: Martin Gudgin [mailto:marting@DEVELOP.COM]
Sent: Thursday, June 07, 2001 9:41 AM
To: SOAPBuilders
Subject: [soapbuilders] XML Protocol: Proposals to address SOAPAction
header


The W3C XML Protocol Working Group is attempting to address perceived and
reported problems with the "SOAPAction" mechanism in the HTTP binding ( see
SOAP 1.1 Section 6.1.1 [1] ). As part of this process, the WG wishes to
solicit
comments and guidance on two proposals it has generated, as below.

Comments must go to xmlp-comments@w3.org by 2001-06-18, and should address
the proposals as they sit, and may optionally make general comments on
resolution of issues with SOAPAction. Those representing the positions of
particular groups or organizations are requested to clearly identify
themselves as such. The WG encourages additional discussion on the
xml-dist-app@w3.org
mailing list.

Neither of the following options precludes equivalent functionality
elsewhere.

Proposal A:
Use of SOAPAction is discouraged.  SOAPAction is an optional part of XMLP,
supported but not required.  Services MAY require SOAPAction and any
software wishing to access those services MUST be able to send it.

Proposal  B:
Use of SOAPAction is deprecated.  Senders SHOULD NOT send SOAPAction.
Receivers MUST NOT accept or reject messages on the basis of the presence,
absence, or value of the SOAPAction header.

Regards

Martin Gudgin
For the W3C XML Protocol Working Group

[1] http://www.w3.org/TR/SOAP/#_Toc478383528









To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
Received on Friday, 8 June 2001 12:52:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:26 GMT