Firstly our environment

• Desktop P.C's communicate over HTTP remoting to server on client side

Example of config file shown below

• Server on client side communicates over HTTP remoting to server at our company

Example of config file shown below

As you can see from the above, we have two clientProviders registered, the one for client to our office using encryption. However, the problem occurs when the server on the bank side raises an event - it appears to use the first entry in the config file despite registering from the client side to use port 4000 (the DesktopToBankServer channel), and to use the soap formatter. Investigation seems to confirm my view. This cause the whole thing to fall over as we are not interested in encryption when raising events.

The solution in this case is to use TCP for communication from the desktops to the client server, but I would be interested if anyone has overcome the problem with events and multiple channels.