ws-rx message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [ws-rx] i089 joint proposal - WSDL
- From: Doug Davis <dug@us.ibm.com>
- To: ws-rx@lists.oasis-open.org
- Date: Thu, 1 Jun 2006 19:40:42 -0400
Yes any soap envelope that the receiver
of the MakeConnection (e.g. the server) deems appropriate to send is a
message. Whether its an app message or just a ack it doesn't matter.
Remember, the only difference between this setup and a normal async
one is how the connection is established - beyond that what message flows
from the server back to the client is up to the server.
-Doug
"Marc Goodner"
<mgoodner@microsoft.com>
06/01/2006 05:35 PM
|
To
| Doug Davis/Raleigh/IBM@IBMUS, <ws-rx@lists.oasis-open.org>
|
cc
|
|
Subject
| RE: [ws-rx] i089 joint proposal - WSDL |
|
So that’s my other related
question on this, in this mechanism is an ack considered a message? You
state in the text that no soap envelope is to be returned if there isn’t
a “message” waiting for the requestor. That sounds like application message,
I’m guessing you consider a ack as a message though.
From: Doug Davis [mailto:dug@us.ibm.com]
Sent: Thursday, June 01, 2006 2:06 PM
To: ws-rx@lists.oasis-open.org
Subject: RE: [ws-rx] i089 joint proposal - WSDL
Its modeled as a one-way - there is no formal response - as in the case
where we hijack a 202 and replace it with an Ack, we hijack the 202 and
replace it with a polled message.
thanks,
-Doug
What does the WSDL for this look like? The proposal says it is one-way
but it seems a response is expected. Shouldn’t it have a response of type
xs:any?
From: Doug Davis [mailto:dug@us.ibm.com]
Sent: Wednesday, May 31, 2006 7:13 PM
To: ws-rx@lists.oasis-open.org
Subject: [ws-rx] i089 joint proposal
All,
the planets have aligned and we managed to come up with a joint proposal
for the TC to discuss on tomorrow's call. Enjoy!
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]