W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2004

Re: Revised Asynch Binding

From: Mark Baker <distobj@acm.org>
Date: Wed, 7 Jul 2004 20:55:23 -0400
To: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Cc: www-ws-desc@w3.org
Message-ID: <20040708005523.GN22429@markbaker.ca>

On Thu, Jul 08, 2004 at 06:31:30AM +0600, Sanjiva Weerawarana wrote:
> I don't think so! Glen/JJM/Gudge/Jack/<any other XMLPers>: What do you
> think?

As an ex-XMLPer who worked on the binding, I have to agree with Sanjiva;
it was clear to me at least, that the intent was as he describes.

The HTTP 202 response could be used to do what the WG needs in terms of
treating the SOAP/HTTP response as an intermediate response, and in fact
the spec specifically calls it out as something that could be supported
... but with a new MEP;

  "Such alternate bindings MAY therefore make use of HTTP features and
   status codes not required for this binding. For example, another
   binding might provide for a 202 or 204 HTTP response status to be
   returned in response to an HTTP POST or PUT (e.g. a one-way "push"
   MEP with confirmation)."
   -- http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#httpoptionality

Mark.
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca

  Seeking work on large scale application/data integration projects
  and/or the enabling infrastructure for same.
Received on Wednesday, 7 July 2004 20:55:02 GMT

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