什么是.NET进程间通信的最佳选择？ [英] What is the best choice for .NET inter-process communication?
问题描述
我应该使用命名管道，或.NET Remoting的与正在运行的进程在我的机器上进行通信？
Should I use Named Pipes, or .NET Remoting to communicate with a running process on my machine?
推荐答案
WCF是最好的选择。它支持许多不同的传输机制的（<一href="http://blogs.charteris.com/blogs/chrisdi/archive/2008/05/19/exploring-the-wcf-named-pipe-binding-part-1.aspx">including <一href="http://blogs.charteris.com/blogs/chrisdi/archive/2008/06/16/exploring-the-wcf-named-pipe-binding-part-2.aspx">Named <一href="http://blogs.charteris.com/blogs/chrisdi/archive/2008/06/23/exploring-the-wcf-named-pipe-binding-part-3.aspx">Pipes)并且可完全配置的推动。我会强烈建议你看看WCF。
WCF is the best choice. It supports a number of different transport mechanisms (including Named Pipes) and can be completely configuration driven. I would highly recommend that you take a look at WCF.
下面是一个博客，做了 WCF VS远程处理性能比较。
Here is a blog that does a WCF vs Remoting performance comparison.
从博客引述：
在WCF和.NET Remoting的在性能上确实具有可比性。差异是如此之小（衡量客户等待时间），它并不重要的一个是快一点。 WCF虽然具有更好的服务器的吞吐量比.NET Remoting的。如果我将开始全新的项目，我就选择了WCF。但无论如何，WCF确实比远程处理，并为所有这些功能我喜欢它更多。
The WCF and .NET Remoting are really comparable in performance. The differences are so small (measuring client latency) that it does not matter which one is a bit faster. WCF though has much better server throughput than .NET Remoting. If I would start completely new project I would chose the WCF. Anyway the WCF does much more than Remoting and for all those features I love it.
这篇关于什么是.NET进程间通信的最佳选择？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
