W3C home > Mailing lists > Public > xml-dist-app@w3.org > August 2000

RE: SOAP spec.: doesn't seem to allow for no return values

From: Satish Thatte <satisht@MICROSOFT.com>
Date: Fri, 4 Aug 2000 13:31:49 -0700
Message-ID: <2DCBFADAFCBBD21189D400805F6FA1AB13D6F9EA@RED-MSG-12>
To: "'Daniel.Barclay@digitalfocus.com'" <Daniel.Barclay@digitalfocus.com>, xml-dist-app@w3.org
Cc: Henrik Frystyk Nielsen <henrikn@MICROSOFT.com>
You are right.  The wording is too strict.  It needs to allow for out
parameters with void return.  One could even think of a degenerate RPC with
neither return value nor out parameters (the "response" being presence or
absence of an exception).  

This should go on the list of spec bugs.

Thanks.

-----Original Message-----
From: Daniel Barclay [mailto:Daniel.Barclay@digitalfocus.com]
Sent: Friday, August 04, 2000 9:09 AM
To: xml-dist-app@w3.org
Subject: SOAP spec.: doesn't seem to allow for no return values



The wording of section 7.1 of the SOAP spec. doesn't seem to
allow for RPC calls that don't have return values.

For example, the fifth list item in section 7.1 says:

  The method response is viewed as a single struct containing an 
  accessor for the return value and each [out] or [in/out] parameter. 
  The first accessor is the return value followed by the parameters in 
  the same order as in the method signature. 

Instead, it should probably using wordig like "for any return value"
or "the return value, if any, ..."


-- 
Daniel Barclay
Digital Focus
Daniel.Barclay@digitalfocus.com
Received on Friday, 4 August 2000 16:33:05 GMT

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