i want to use Remoting for IPC (inter process communication).
I thought that the most flexible Exchange (remoted) object would be a
singleton implementing the Dictionary(K,T) interface (K & T being exposed
generic key and data types).

I am trying to intercept local calls to objects.  I have found 3 ways to do
this and they all stink.  The root of the problem is that it forces users of
my implementation to derive from MarshalByRef or ContextBoundObject.  This
will not work.

I have to apps that communicate using remoting. This works fine on a
single machine.
When I run the same on a terminal server I get an error when
registering a channel, when the second client starts the application.

I have a singleton server side object published by .Net C# remoting.
In the client side after creating the object, how can I know when the server
is down by receiving connection down event?
The server does not have a keep alive method that I can call every X seconds

What could be a problem when ISponsor.Renewal is not geting called if
remoting server is not in the same computer that remoting client. If I
put remoting server to same machine than client ISponsor.Renewal is
geting called.