Two-way interprocess communication (through named pipes) - WCF or .Net Remoting?

I have what seems like a fairly common requirement for interaction between processes - the parent process spawns some child processes, and the parent process and child processes should be able to perform two-way communication with each other (the child process needs the parent process to be updated with its state, and the parent process had to check that the child process is still alive - note that the child processes should not communicate with each other).

I do this using WCF, but I am new to using WCF for this type of IPC - as far as I can tell, to get this two-way communication, I will need both a parent process and a child process to expose WCF services that seem a bit fake.

On the other hand, .Net Remoting makes such communication almost seamless, but everyone seems to think that Remoting is an old hat, and I should use WCF instead.

Therefore, I struggle to choose the approach that I must take: - My goal is to make the message as simple as possible. - Security is not really a problem.

What to choose?

+3
source share
2 answers

, . API-:

  • Remoting , , .
  • WCF , , .

WCF , , . , , Remoting.

, WCF , . , .. , , WCF.

WCF , .

+4

, ( ).

, .NET Remoting, , () WCF.

0

Source: https://habr.com/ru/post/1773787/


All Articles