DDE 的用途和替代方案？
我在win98时代尝试使用DDE，当时我切换到了XP。我无法安静地让它工作，也不知道它可以或应该用来做什么。
我想知道我可以使用什么替代方案？当时我想制作 3 个应用程序，无论它们以什么顺序打开，它们都可以与其他应用程序进行通信。我最终让他们都启动了一个单实例服务器应用程序，所有 3 个应用程序都使用该应用程序与服务器应用程序相互通信。 DDE 更适合吗？
无论如何，DDE 的替代品是什么？我阅读了动态数据交换（DDE） - 仍然相关吗？ 其中提到了 COM，但我不知道它们是什么或如何使用它们。它们也与我上面的情况相关吗？
DDE 的替代品是什么？感觉TCP（或命名管道）+窗口消息+全局内存可以解决任何IPC问题。
I tried using DDE back in the win98 days around the time i switched to XP. I couldnt quiet get it to work nor know exactly what it can or should be used for.
I want to know what alternatives could i use? Back then i wanted to make 3 apps which can communicate to the others no matter what order they were opened. I ended up having them all launch a single instance server app which all 3 use communicate to eachother to the server app instead. Is DDE better suited for that?
Anyways what are alternatives to DDE? i read the answer to Dynamic Data Exchange (DDE) - Still Relevant?
which mentioned COM but i dont know what they are or how to use them. Also would they be relevant to my situation above?
What are alternatives to DDE? It feels like TCP (or named pipes)+Window Messages+Global memory can solve any IPC problem.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
对于具有位置独立性的特定于 Windows 的进程间通信方案，您的最佳选择是 Windows Communication Foundation (WCF)。这不仅仅是网络服务。
例如，您可以在没有 IIS 的情况下托管 Web 服务。您可以在项目中使用 svc 文件来支持 AJAX 调用。
如果在windows环境下需要IPC，请使用WCF。
Your best bet for a Windows-specific interprocess communication scheme with location independence is Windows Communication Foundation (WCF). It's not just web services.
For example, you can host a web service without IIS. You can use a svc file in your project to support AJAX calls.
If you need IPC in a windows environment, use WCF.
由于多种原因，DDE 无疑是一项即将消亡的技术。也许其中一些原因使您在尝试使用它时感到困难。
您没有指定您使用的是哪种语言，因此很难猜测哪种替代方案最适合您。但是，是的，命名管道、TCP/IP、全局内存等将是与语言无关的替代方案。
如果您使用的是 .NET Framework，那么您的选择将包括 .NET Remoting 或较新的技术 Windows 通信基础 (WCF)。
DDE is definitely a dying technology for many reasons. Perhaps some of those reasons made it difficult for you when you attempted to use it.
You did not specify which language you were using so it is hard to guess which alternatives might be best for you. But, yes, named pipes, TCP/IP, global memory, etc. would be language agnostic alternatives.
If you were using the .NET Framework then your choices would include .NET Remoting or the newer technology Windows Communication Foundation (WCF).