简体繁体 English

命名管道是否适合这种情况？

[英]is a named pipe right for this situation?

原文 2015-11-19 06:42:36 8 1 c#/ c++

There are 3 projects: MyEXE and MyDLL in C#, and TheirEXE in C++. 有3个项目：C＃中的MyEXE和MyDLL ，以及C ++中的他们的TheirEXE 。

All three projects are on the same computer, which I can upgrade if required. 所有三个项目都在同一台计算机上，如果需要，我可以对其进行升级。 I use TheirEXE every day. 我每天都使用他们的TheirEXE 。 I plan to get TheirEXE to use MyDLL for added functionality. 我计划让他们的TheirEXE使用MyDLL来添加功能。 I was told I would need to write a C++ wrapper for MyDLL because TheirEXE is COM . 有人告诉我我需要为MyDLL写一个C ++包装器，因为他们的TheirEXE是COM 。 The details are frankly over my head but they will help so I assume it will work. 坦白地说，这些细节非常有用，但是它们会有所帮助，所以我认为它会起作用。

If I can get TheirEXE to reference MyDll , then I want a fast named pipe or some form of fast data transfer between MyDLL and MyEXE , capable of transferring in either direction a few dozen distinct 50 to 200 byte packages per second with high reliability. 如果我可以让他们的TheirEXE引用MyDll ，那么我想要一个快速的named pipe或MyDLL和MyEXE之间的某种形式的快速数据传输，能够以MyEXE两个方向传输数十个不同的50到200字节的程序包，并且具有很高的可靠性。

Security is not an issue. 安全性不是问题。 Is this possible? 这可能吗？ Many thanks in advance for any help! 在此先感谢您的帮助！

1 个解决方案

You can use named pipe or even a standard TCP-Socket (what way it would be ready to do it remote). 您可以使用命名管道，甚至可以使用标准的TCP-Socket（以何种方式可以进行远程操作）。 I personally would go for the TCP-Socket but its a matter of personal taste I would say. 我个人会选择TCP-Socket，但是我要说的是个人喜好。