Default bindings
Connect to the Core Service from your SOAP, WCF or network client using the default bindings BasicHttpBinding (SOAP), WSHttpBinding (WCF) or NetTcpBinding (network).
BasicHttpBinding-
Use
BasicHttpBindingif you require your service to be consumed by clients compatible with SOAP 1.1. This type of binding is functionally most restricted, but most supported and interoperable. WSHttpBinding-
Use
WSHttpBindingif your service can be consumed by SOAP 1.2 clients. This is the functionally richer option, specifically offering support for the following features (which do not work with theBasicHttpBindingtype):- transaction support
- session support (which is needed for impersonation and for transaction timeouts)
- (message-based) security
- support for the Web service standards "WS-Atomic Transaction" and "WS-Security"
NetTcpBinding-
You can only use
NetTcpBindingif you are connecting from .NET. This binding type performs better thanBasicHttpBindingorWSHttpBindingbut requires more open ports in your firewall. For this reason, it is typically used when the client is on the same machine as the server and implements server-side logic, but is not hosted inside the Content Manager Kernel host; that is, is not Template code or Event Handler code.Typical examples of clients that could use aNetTcpBindingare:- GUI extensions (Data Extenders or Custom Pages)
- Custom tools or integration intended to be run on the Content Manager server
The file %TRIDION_HOME%\web\WebUI\WebRoot\web.config includes a number of out-of-the-box, predefined configuration for the Core Service net.tcp endpoints.