If you need to support remote WCF clients within an intranet, consider using netTcpBinding
J.D. Meier, Jason Taylor, Prashant Bansode, Carlos Farre, Madhu Sundararajan, Steve Gregersen
If you need to support clients within your intranet, consider using netTcpBinding. netTcpBinding is a good choice for the intranet scenario if transport performance is important to you and it is ok to host the service in a Windows service instead of in IIS. The netTcpBinding uses the TCP protocol and provides full support for SOAP security, transactions, and reliability. Use this binding when you want to provide a secure and reliable binding environment for .NET-to-.NET cross-machine communication.
The netTcpBinding has the following characteristics:
- It can only be consumed by WCF enabled clients.
- Supports the WS* stack including reliable messaging, message security, and secure transactions.
- Transport security is turned on by default, message security is also available.
- The service cannot be hosted in IIS, you can host in a Windows service instead.
- If you choose to use message security you can use certificates, username, Windows or token authentication
- If you choose to use transport security you can only use certificates or Windows authentication
The following example shows a netTcpBinding configuration section:
<binding name = “myNetTcpBinding”>