0

I have a process (B) that I wish to act as both a .NET remoting client and server. In other words, this process will connect via .NET remoting to a server (C), as well as expose itself via .NET remoting to clients (A). For example:

A --> B --> C

Is this possible? Here's a snippet for my configuration file for B:

    <channel ref="tcp" port="0" secure="true" tokenImpersonationLevel="impersonation"/>
    <channel ref="ipc" portName=..../>

A tcp channel has been configured because B must connect to C using impersonation. An ipc channel has also been configured so that local clients (A) may connect to B. But won't .NET remoting see both ports and expose server objects on both ports for B? If so, how can I restrict it to use just the ipc channel for the server?

And just to preempt all you WCF enthusiasts -- I would be interested in pursuing WCF, but only if it offers the only solution. I am not interested in it just for the sake of using a newer technology.

Dan
  • 1,215
  • 1
  • 10
  • 22
  • Why would you think that a client channel would be exposed through a server channel? Also I suggest you look at [these questions](http://stackoverflow.com/search?q=wcf+vs+remoting) before ruling out WCF. . – Conrad Frix May 21 '12 at 22:04
  • My understanding was, in the case of a server, that all registered objects were exposed via the channels listed in the remoting configuration -- that there is no way to specify "this is a client channel and this is a server channel". Is this not true? – Dan May 21 '12 at 22:23

0 Answers0