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

Re: One-way messaging in SOAP 1.2

From: Edwin Ortega <ortegae@wns.net>
Date: Wed, 16 Jan 2002 13:25:24 -0800
Message-ID: <00b101c19ed4$521d6cc0$32a2583f@val6000>
To: "Marc Hadley" <marc.hadley@sun.com>, "XML dist app" <xml-dist-app@w3c.org>

----- Original Message ----- 
From: "Marc Hadley" <marc.hadley@sun.com>
To: "XML dist app" <xml-dist-app@w3c.org>
Sent: Wednesday, January 16, 2002 3:18 AM
Subject: One-way messaging in SOAP 1.2


> All,
> 
> I'd like to raise a new issue:
> 
> In Part 1, section 5.3 we find:
> 
> "Every binding specification MUST support the transmission and 
> processing of one-way messages as described in this specification. A 
> binding specification MAY state that it supports additional features, in 
> which case the binding specification MUST provide for maintaining state, 
> performing processing, and transmitting information in a manner 
> consistent with the specification for those features."
> 
> This paragraph is potentially confusing, either we mean:
> 
> (i) All bindings must support a one-way MEP, in which case there are two 
> issues:
>    (a) we currently don't define a one way MEP in the specification
>    (b) the HTTP binding we do define doesn't support a one-way MEP
> 
> or (my reading)
> 
> (ii) All bindings must at a minimum define how to move a message from 
> one node to another, in which case I would propose that we add a 
> clarification along the lines of "Note, this does not mean that all 
> bindings must support a one way MEP, only that they MUST define how to 
> move a message from one SOAP node to another".
> 
> Comments ?
> 
> Regards,
> Marc.
> 
> 
> 
Received on Wednesday, 16 January 2002 12:41:04 GMT

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