netTcpBinding或wsHttpBinding

问题描述

我有一个作为Windows服务托管的WCF服务，客户端是一个使用WCF服务方法的ASP.Net应用程序.

在实现安全性的过程中，我感到困惑的是netTcpBinding/wsHttpBinding中哪一个适合我的情况.

场景中的所有应用程序(WCF服务，Windows服务，ASP.Net网站)很可能会位于我们办公室的不同服务器上，从而位于内部网中.用户可以通过Internet访问ASP.Net网站.

尽管，我总是可以在这里使用wsHttpBinding，在我的情况下使用netTcpBinding设置服务端点是否合适?

解决方案

检查一下，以比较所有不同的内置绑定:

配置系统提供的绑定-MSDN

对于您的情况，只要是与WCF服务联系的Web服务器，并且您不需要为该服务的任何外部使用者提供端点... netTcpBinding应该就可以了./p>

I have a WCF Service hosted as Windows Service and client is an ASP.Net application consuming WCF Service methods.

In process of implementing security, I am confused over which among netTcpBinding/wsHttpBinding will be suitable for my case.

Most likely all the applications in scene (WCF Service, Windows Service, ASP.Net Website) will be sitting on different servers in our office, thus in an Intranet. ASP.Net website will be accessed by users over Internet.

Though, I can always use wsHttpBinding here, will it be suitable to set the service endpoint using netTcpBinding in my case?

解决方案

Check this out for a comparison of all the different built in bindings:

Configuring System-Provided Bindings - MSDN

As for your case, as long as it's the web server contacting the WCF service and you don't need to provide an endpoint for any external consumers of the service...netTcpBinding should be up to the job.

这篇关于netTcpBinding或wsHttpBinding的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！