All geek questions in one place

The easiest way to quickly get RPC with .NET?

What is the easiest way to get RPC in .NET? I see that there are .NET Remoting and WCF, and according to Wikipedia, WCF is the successor to .NET Remoting.

So far, I have only tried removing things that seem pretty simple - so far I have not encountered any application speed problem. Is .NET removal really the best way to get RPC to work, or should I have a peek at WCF (since will remote .NET start stop in favor of this?)? I only need to communicate with already known objects written in C #, so I do not need any of these XML / SOAP /, etc. transport format. The target application is intended for distribution over the network and only communicates with the instances themselves. In this context, I just want to connect to an object somewhere without having problems with protocol level issues.

+2
source share
2 answers

You can use WCF with binary formatting and TCP binding. If this is (still) not fast enough, you will have to look at custom (non-standard) technologies. For communication on 1 machine, you can use the IPC protocol (which is similar or based on named pipes).

Indeed, Remoting disappears as a separate method. It is assimilated by WCF.

+3
source

As soon as I read the discussion somewhere on CP, I think, and someone proved that WCF using channels (which allows you to run IPC on only one computer) is much faster than .Net Remoting and when using tcp - it's a little faster. I can’t confirm this is true for all cases, but you can use Google for some tests, I have seen a little. Under my assumption, if the remote gives you everything you need, you can stick with it, at least for now :).

+2
source

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

More articles:


All Articles