That looks like you're looking for the duplex sample in the SDK. The client uses a oneway call to the server and passes the return address in the <From> element. When the server is ready to reply it makes another oneway call back to the client using the address it received in the first message from the client.
Thus you get your asynchronous behaviour. If you look at the envelopes they will look simliar to this:
I made my own duplex sample and it works. Now, I read some articles about WS-Addressing, so I have some knowledge about it. How can I demonstrate it within my duplex communication channel
I
was playing with OperationContextScope() and
OperationContext.Current.OutgoingMessageHeaders on the clients side
and OperationContext.Current.RequestContext.RequestMessage.Headers on
the server side.
I could add additional headers and display them but is that enough to demonstrate ws-addressing purpose
WS-Addressing
jamesbrowne
http://mdavey.wordpress.com/2005/11/28/wcf-duplex/
(duplex communication)
and this
http://www.webserviceshelp.org/wsh/Standards/Web+Services+Addressing/
(WS-Addressing)
Cheers!
[melack]
Aparna496
I'm trying to do an asynchronus client callback with WS-Addressing.
Tariq Ayad
Where can I find them
[melack]
Walt Ritscher
What you can do to see your envelopes is set up a message logger.
http://windowssdk.msdn.microsoft.com/library/en-us/WCF_Con/html/0ff4c857-8f09-4b85-9dc0-89084706e4c9.asp frame=true
Once you have your traces, you can view them in the svctraceviewer tool.
http://windowssdk.msdn.microsoft.com/library/en-us/WCF_tools/html/9027efd3-df8d-47ed-8bcd-f53d55ed803c.asp frame=true
Thanks,
Scott
SNNicky
Thanks.
[melack]
Gato00
That looks like you're looking for the duplex sample in the SDK. The client uses a oneway call to the server and passes the return address in the <From> element. When the server is ready to reply it makes another oneway call back to the client using the address it received in the first message from the client.
Thus you get your asynchronous behaviour. If you look at the envelopes they will look simliar to this:
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm" xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">
fel lobo
Here's the sample:
http://windowssdk.msdn.microsoft.com/library/default.asp url=/library/en-us/WCF_samples/html/bc5de6b6-1a63-42a3-919a-67d21bae24e0.asp
If your goal is to demonstrate WS-Addressing, you should also look at the routing sample.
http://windowssdk.msdn.microsoft.com/library/en-us/WCF_samples/html/768e73c6-1a95-4741-8697-e22acc034ef1.asp frame=true
Thanks,
Scott
SCIMalta
I made my own duplex sample and it works.
Now, I read some articles about WS-Addressing, so I have some knowledge about it.
How can I demonstrate it within my duplex communication channel
I was playing with OperationContextScope() and OperationContext.Current.OutgoingMessageHeaders on the clients side and OperationContext.Current.RequestContext.RequestMessage.Headers on the server side.
I could add additional headers and display them but is that enough to demonstrate ws-addressing purpose
[melack]
tjcbs
Hi Scott,
The 1st link is unavailable. Could you post an existing WS-Addressing sample link
Thanks,
Hellen
Nick P
What are you trying to do specifically
Thanks