I am well aware that the Rest based approach is targeting HTTP. I would love to use the REST APIs and other goodness between processes on the same computer. Since ADO.NET data services is built on top of WCF it would seem reasonable to assume that the transport in configurable to work with any of the WCF supported transports. Anyone know if there is a way to configure it to send traffic via namedpipes?
我很清楚基于Rest的方法是针对HTTP的。我很乐意在同一台计算机上使用REST API和进程之间的其他优点。由于ADO.NET数据服务构建在WCF之上,因此假设传输可配置为与任何WCF支持的传输一起使用似乎是合理的。有人知道是否有办法配置它通过namedpipes发送流量?
2 个解决方案
#1
2
Actually the REST architectural style does not in any way require HTTP. That just happens to be the most common implementation protocol. However, ADO.Net data services uses System.ServiceModel.Web which IS tied to http. You can certainly do REST over named pipes, you will just have to find a different protocol.
实际上,REST架构风格不以任何方式需要HTTP。这恰好是最常见的实现协议。但是,ADO.Net数据服务使用与http绑定的System.ServiceModel.Web。您当然可以通过命名管道执行REST,您只需要找到不同的协议。
#2
0
In .NET 3.5 there is built-in named pipe binding for WCF. See the MSDN for details.
在.NET 3.5中,存在用于WCF的内置命名管道绑定。有关详细信息,请参阅MSDN。
#1
2
Actually the REST architectural style does not in any way require HTTP. That just happens to be the most common implementation protocol. However, ADO.Net data services uses System.ServiceModel.Web which IS tied to http. You can certainly do REST over named pipes, you will just have to find a different protocol.
实际上,REST架构风格不以任何方式需要HTTP。这恰好是最常见的实现协议。但是,ADO.Net数据服务使用与http绑定的System.ServiceModel.Web。您当然可以通过命名管道执行REST,您只需要找到不同的协议。
#2
0
In .NET 3.5 there is built-in named pipe binding for WCF. See the MSDN for details.
在.NET 3.5中,存在用于WCF的内置命名管道绑定。有关详细信息,请参阅MSDN。