W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

i028: RE: i028: Implications of the presence of ReplyTo

From: Jacques Durand <JDurand@us.fujitsu.com>
Date: Thu, 11 Nov 2004 18:44:41 -0800
Message-ID: <6DDD4D6558F5704A89316276BAAD81221478C184@exchange.regatta.fswroot.fsw.fujitsu.com>
To: "'Brinild'" <brinild@yahoo.com>, public-ws-addressing@w3.org
But the presence of "ReplyTo" does not necessarily mandate a [WSDL]
Request-response operation type:
aren't we talking of possibly long-lasting MEPs, asynchronous
(e.g. implemented as two separate One-way calls in opposite directions)
where the application logic behind the WS operation needs be given a
response address?
(and i030 makes the case that precisely, ReplyTo may not be needed with a
[WSDL]request-response type)

 So I believe a message with ReplyTo and a message without, could both be
carried over a One-way message.

Now the problem I see with ReplyTo, is that the requirement of including a
ReplyTo element must be operation-specific, not WS-specific. 
For the same WS instance, operation A may require it, operation B may not.
As a user, how will I know that I "MUST include ReplyTo" for A? Shouldn't
the EPR tell me that?

Fujitsu Software

-----Original Message-----
From: Brinild [mailto:brinild@yahoo.com]
Sent: Thursday, November 11, 2004 6:03 PM
To: public-ws-addressing@w3.org
Subject: RE: i028: Implications of the presence of ReplyTo

--- Martin Gudgin <mgudgin@microsoft.com> wrote:
>...And I don't think MEP semantics
> should be inferred from the presence/absence of wsa:
> headers ( although
> the set of such headers could be infered, or even
> explicitly stated, for
> a given MEP ).

Too bad.  The idea of having a self-describing soap
envelope has its appeal.  Also, knowing if its a
response MEP by looking at the message can eliminate
some ambiguity; for example in cases where there are
two port-types with the same operation, one as a
request/response and one as a one-way.


Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
Received on Friday, 12 November 2004 02:49:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:28:21 UTC