This project is read-only.

If You Need to Support WCF Clients within an Intranet, Consider Using netTcpBinding

- J.D. Meier, Carlos Farre, Jason Taylor, Prashant Bansode, Steve Gregersen, Madhu Sundararajan, Rob Boucher

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 as 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 can be hosted in IIS 5.0 or IIS 6.0, but it is not message activated, hence you can consider hosting in a Windows service or IIS 7.0 instead.
  • If you choose to use message security you can use certificates, username, Windows or Issue token authentication (Windows CardSpace).
  • If you choose to use transport security you can only use certificates or Windows authentication

The following example shows how to configure netTcpBinding:
<system.serviceModel>
....
    <services>
        <service behaviorConfiguration="" name="WCFServicecHost.MyService">
            ...
            <endpoint address="" binding="netTcpBinding" bindingConfiguration=""
                name="TcpBinding" contract="WCFServicecHost.IMyService" />
            ...
        </service>
    </services>
</system.serviceModel>

Additional Resources

Last edited Jun 12, 2008 at 10:11 PM by prashantbansode, version 1

Comments

No comments yet.