WCF: Are asynchronous calls safer?

Question

In the project that I am currently working on, we use WCF. Company policy forces us to use asynchronous calls, and the reason must be security. I asked why this is much safer, but I do not get clear answers.

Can someone explain why this is so safe?

Answer 1

This is not true. The same mechanisms and security considerations (authentication, encryption) apply regardless of whether the call blocks until a response is received or uses a callback.

, - , , "/", , WCF , , ,

, , , . .

Answer 2

, , . , .

Answer 3

, , . , , async .

, - ?

Answer 4

- .

Fiddler . ( , , , ). , .

Fiddler - , . , .

Answer 5

WCF (BeginBlah/EndBlah) . ,

[OperationContract(AsyncPattern=true)]
IAsyncResult BeginSomething(AsyncCallback, object)

void EndSomething(IAsyncResult)

... "-". WCF: , / .

, WCF (, Add Service Reference), , , , . , , .

, WCF, , , : , WCF , . , , . : NetTcpBinding .

, , , - WCF. async ( -, - ), , , , DOS- ( WCF IO), .

. MSDN

Note. If you share the contract interface between the client and the server, then obviously the synchronization of both ends is appropriate (because they both use the same type of interface), but this is just a limitation on the use of a common interface. If you made another equivalent interface that differs only in an asynchronous template, you could still create a ChannelFactory against it simply.