Hi, I have a very simple WCF service application.
Where are a whole bunch of services, and they all "chatter" to each other using basicHttpBinding
The configuration looks something like this (I've changed it here from what it really is to keep it simple for my question).
<endpoint address="" binding="basicHttpBinding" contract="com.company.prod1.I12">
<dns value="localhost" />
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
<add baseAddress="http://localhost:80/CompanyName/ProductName/I1123" />
Each of the services chatters to another WCF service application.
Some service applications are configured using basicHttpBinding
Others are configured using WsHttpBinding, and netTcpBinding
The reason for the differences is that the services are deployed on different computers, and there are some existing firewall rules that don't allow me to choose the same protocol etc
for every service.
Some of my existing bindings also have timeouts, see http://msdn.microsoft.com/en-us/library/hh924831(v=vs.110).aspx
My question is is there a way to setup multiple bindings, so that
"magically" the service and the client (another service) try a whole bunch of bindings with timeouts configured and eventually fail over/find to the one that works and use that, ie.
first try basicHttpBinding
, with a timeout, if that works communicate that way, otherwise try the next one in the list, and so on and so on. When specifying netTcpBinding
I would like to also specify - try these port number ranges, eg. 8000 - 8500 but not all the others.
Is this possible?