W3C home > Mailing lists > Public > xml-dist-app@w3.org > May 2001

Re: Issue 16: methods with void return type and no out params

From: Mark A. Jones <jones@research.att.com>
Date: Fri, 25 May 2001 10:58:40 -0400
Message-ID: <3B0E7320.BBEA87BD@research.att.com>
To: Frank DeRose <frankd@tibco.com>
Cc: xml-dist-app@w3.org
Frank,

Isn't it possible that there will be intermediaries in the return path
of a SOAP RPC call that may want to insert headers or otherwise process
the return message?  If we don't always return a valid message, this
would be a problem for behavior 1.

Frank DeRose wrote:

>  I have been asked by the WG to seed discussion on issue 16 from the
> issues list [1].
>
> Bryan Murray, the author of  issue 16, asserts that Section 7.1 of the
> SOAP spec [2] does not explicitly state how a method with a void
> return type and no out parameters should be mapped onto the SOAP
> protocol. Bryan conceives of four possible behaviors:
>
> 1.      return HTTP 204 No Response
> 2.      return an empty SOAP Envelope
> 3.      return an empty SOAP Body
> 4.      return an empty SOAP method response
>

--
Mark A. Jones
AT&T Labs - Research
Shannon Laboratory
Room A201
180 Park Ave.
Florham Park, NJ  07932-0971

email: jones@research.att.com
phone: (973) 360-8326
  fax: (973) 360-8970
Received on Friday, 25 May 2001 10:57:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:01 GMT