Is there any advantage in using duplex WCF service rather than dual request-response

Question

0.00/5 (No votes)

See more:

In our application we have several clients that request services from a single server. Usually, the client gets a UI update from the server so we want the client to disallow additional UI requests while waiting for a server response. Following a data change that was initiated by one client, the server updates all the clients that are affected by the data change (Have open windows that need to be refreshed).

In the above environment, is there an advantage in using duplex WCF service rather than two way request-response services.

Thanks, Micha

Posted 29-Dec-11 4:15am

Micha Miz

Add a Solution

Comments

Sergey Alexandrovich Kryukov 29-Dec-11 11:34am

Not 100% clear -- you might need to explain the alternatives in more detail. Better yet, explain your ultimate goals. How do you know, maybe people can give your better alternatives. Also, you should understand: the choice of solution depends on purpose. So, you can use "Improve question" above.
--SA

TRK3 30-Dec-11 15:09pm

I briefly experimented with WCF's duplex service and ran into problems with both directions being blocked when one direction was waiting on a response. That was not desireable in my application.

At the time I couldn't see anyway around and went with two separate request-response pipes (one in each direction).

Maybe I was just configuring my WCF service wrong or doing something else wrong, but I found that rolling my own gave me better control of what I wanted to do.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)