How to enable reliability for one-way methods?

What you need to know about one-way calls, callbacks and events , the article says:

The fact that the client does not care about the result of the call does not mean that the client does not care if the call was called at all. In general, you must enable the reliability of your services, even for unidirectional calls.

I tried to find a way to enable reliability, but did not find anything meaningful.

Could you help me:

  • How to enable reliability?
  • How to check if a server has reached unilaterally?

Thank you so much!

+3
source share
3 answers

, Message Reliability, "" WCF" - (, , , , ).

. TCP. :

<binding>
    <netTcpBinding>
        <binding name="MyTcpBinding">
            <reliableSession enabled="true" />
        </binding>
    </netTcpBinding>
</binding>

, (. 66):

. , , .

, , , , , , .

:

http://msdn.microsoft.com/en-us/library/ms733136.aspx

+2

@Budda: , . . , : - - - " ", , . , , . , , , wcf, . , , . , wcf; , , , . , " ".

0

Usually, if you need OneWay operations and reliability, this is a good sign that you are building a queue based mechanism. The customer queues the message, workers select the messages and process them.

Perhaps you could take a look at MSMQ and see if it can help you.

In most cases, OneWay operations do not have to carry an important task or information, since they are inherently not guaranteed to be processed by the server. OneWay causes a client-side refund when a message is sent by the service-side dispatcher. After the dispatcher, you have no reliability.

0
source

All Articles