TCP 连接和防火墙
在互联网上，如果你需要快速， 安全的服务器到服务器通信， 并且您可以指定哪个防火墙 端口开放，NetTcpBinding可以 事实证明非常有价值。
a) 文本是否暗示使用某些其他连接协议（例如 HTTP），我们不需要检查开放的防火墙端口？
b) 为什么NetTcpBinding仅适用于服务器到服务器的通信，而不适用于客户端到服务器的通信？
谢谢
On the Internet, if you need fast,
secure server-to-server communication,
and you can specify which firewall
ports are open, NetTcpBinding can
prove very valuable.
a) Is text implying that with some other connection protocols, such as HTTP, we don't need to check for open firewall ports?
b) Why would NetTcpBinding only be useful for server-to-server communications, but not for client-to-server communications?
thank you
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
a) 当您部署到企业时，您通常无法控制其外部防火墙。其防火墙的设置是由网络管理员按照企业范围的策略进行的。外部防火墙几乎总是允许传出 HTTP 请求（否则您无法浏览网页）。某些公司防火墙会阻止传出 TCP 请求，这意味着您无法使用 netTcpBinding。例如，如果有人尝试，请参阅此问题来处理这个问题。如果您知道每个客户的防火墙都允许传出 TCP，那么 NetTcpBinding 是一个合适的选择。
b) 谁说 NetTcpBinding 仅适用于服务器到服务器的通信？您可以将客户端-服务器应用程序部署到企业中，并且假设客户端和服务器都位于 Intranet 内，那么 NetTcpBinding 是一个合适的绑定选择。
a) When you deploy to an enterprise, you usually don't have control over their external firewall. The setup of their firewall is made by network administrators following an enterprise wide policy. External firewalls almost always allow outgoing HTTP requests (otherwise you couldn't browse the web). Some corporate firewalls block outgoing TCP requests, which means you cannot use netTcpBinding. As an example, see this question for somebody trying to deal with that issue. If you KNOW that the firewall of every one of your customers will allow outgoing TCP, then NetTcpBinding is an appropriate choice.
b) Who says NetTcpBinding is only useful for server-to-server communications? You can deploy a client-server application into an enterprise, and providing the clients and the servers are all within the intranet, then NetTcpBinding is an appropriate choice of binding.