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 BasicHttpBinding if 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 WSHttpBinding if 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 the BasicHttpBinding type):

  • 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 NetTcpBinding if you are connecting from .NET. This binding type performs better than BasicHttpBinding or WSHttpBinding but 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.