通过非.net App的命名管道进行WCF通信 [英] WCF Communication though named pipes with non .net App

问题描述

我听说WCF是.net中跨网络和应用程序通信的新标准.这个想法似乎也很有意义，它为程序进行通信提供了标准接口.

I hear that WCF is the new standard for communication across the network and applications in .net. The idea seems to make sense as well, provide standard interfaces for programs to communicate.

这是我的情况，我有一个.net应用程序，我想通过管道与ruby应用程序进行通信.在.net方面(服务器)，我想使用WCF，而在ruby方面(客户端)将使用口香糖和胶带.

Here is my situation, I have a .net app i want to communicate to a ruby application though pipes. On the .net side (server) I would like to use WCF while the ruby side (client) will be chewing gum and duct tape.

我认为两端都不需要是WCF，但是进行这项工作将涉及什么. WCF是否期望收到传入请求的标准协议?

I assume both ends don't need to be WCF but what will be involved in making this work. Is there a standard protocol WCF expects incoming requests?

推荐答案

可以为非WCF客户端使用命名管道绑定 ，但这并非易事.您需要以正确的格式发送消息，以便WCF使用.

Using the named pipes binding for non WCF clients could be possible, but it wouldn't be easy. You'd need to send the messages in the correct format for WCF to consume.

首先参见此第一或关于WCF消息的最后一个条目框架暗示复杂性.这不是不可能，但是值得付出努力吗?

See this first or last entry on WCF message framing for a hint at the complexity. It's not impossible, but is it worth the effort?

推荐使用http传输+某种类型的文本或标记编码，例如basicHttpBinding或webHttpBinding.

Recommended is the http transport + some type of text or markup encoding, like basicHttpBinding or webHttpBinding.

这篇关于通过非.net App的命名管道进行WCF通信的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！