What .net infrastructure to use for communication between two processes

I am working on an application where I have an image verification process and a Ui process. Both are programming using C # 4.0. They may or may not be on the same machine. I have to develop it to handle both methods. The verification process will essentially be performed as a server in this application in a 7/64 window.

In terms of communication, messages from Ui to the verification process will be minimal. Mostly start / stop / update type messages. When the verification process is verified, it can transfer up to 10 mb / s of images for continuous monitoring.

In SO 468375 , if both processes are on the same machine, it is recommended to use Named Pipes. Sounds like a good solution.

However, my real question is: what is the currently recommended best practice for exchanging data between the two processes, if they are on different computers. WCF service, sockets, remote connections, named pipes, etc.?

+3
source share
4 answers

Removal is outdated. WCF encapsulates Remoting, Web Services, and other older communications technologies.

Edit - added the following paragraph

WCF . - Remoting .. , , LINQ. LINQ : SQL-, , XML ..

, WCF , . , .

+10

re David .

, WCF . ( .Net 4.0). TCP , , .

.

+3

, MSMQ. , , .net.

+1
0

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


All Articles