I have a WCF server that unveils an interface that has a call-back interface that sends events to the client Uses for
I do not mark all the methods in the form of "one-way" on call-back interface, because it does error tracking and hard logging.
The client is written in WinForms, so call-back will not process, until the server returns after calling. (This is the behavior that I want)
I make all calls back with Asynchronous Eg StartMyMethod (...), so the server is waiting for the client is not blocked .
However, if the call-back is sent to the same client as the request has been sent to the server, then the TCP channel delivers it to itself, because the customer has to send the feedback back to the customer. It does not seem to be able, before the customer has sent back the call-back response to the server on the same channel.
You can do this if both the server and the client both a server and the client (such as that makes sense) acks
This will work like this:
- When the customer starts the call to the server and registers itself
- The server knows where the client is and can contact the client through the services displayed by the customer.
Another, simple addition Re Paddy channels will not be used, thereby avoiding deadlock.
No comments:
Post a Comment