Thanks for the responses Mike and Ming. Mike - your solution works on the server side great - I was able to get the two different channels serving the same object instances to two different clients - pretty cool. But I still can't see how to easily get it to work on the client side, since on channels for the client side shouldn't be assigned a port - hence up to the runtime to decide which channel to use when connecting. I was hoping for an easier solution, but maybe Ming's suggestion isn't as difficult as it sounds - I'll take a look at that approach. I don't understand the usefulness, at least on the client side, of having multiple channels of the same type if remoting doesn't have the intelligence to select. I'm surprised there is no "out of the box" solution to this one. It doesn't seem like that unlikely of a scenario.
You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
