.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 是最佳选择.它支持多种不同的传输机制(包括 命名 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 与远程处理性能比较.
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屋！
