Remoting the same object to two URIs

Question

0.00/5 (No votes)

See more:

Due to external constraints, I have to provide remoting access to the same object through two URI's. Omitting all the remoting configuration (which does seem to set up correctly), the general idea is:

m_RemotedComponent = new RemotedComponent();
RemotingServices.Marshal(m_RemotedComponent, remotingName1);
RemotingServices.Marshal(m_RemotedComponent, remotingName2);

The two connections provide different interfaces that the one component supports.

Regardless of which order the two Marshal statements appear, the first one works and the second one doesn't. Upon connecting to the second URI, I get the error message saying that the object has to derive from MarshalByRefObject. But, since I can always instantiate the first-listed URI successfully, it obviously does derive from that. If I create a second RemotedComponent, I can marshal it successfully to the second URI, so the problem is clearly related to trying to marshal the same object to two URI's.

Is this supposed to be possible? If so, how?

Posted 10-Aug-10 11:38am

John Whitmire

Add a Solution

Comments

John Whitmire 11-Aug-10 15:32pm

OK, a little more experimenting revealed that I don't need the two URIs after all; I can make it work with just one. This is now just a curiosity question.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ron Beyer · Accepted Answer · 2010-08-19T11:00:00

It definitely is possible, but it requires a lot more code-behind than what you have above. In general, the process is:

1. Create a Hashtable with the properties set (port and name specifically) for each Channel.

2. Create each channel using the hash table. For example you can create two TCPServerChannel's, or one TCPServerChannel an an IPCServerChannel, etc.

3. Call RemotingServices.Marshal(objref, channelName) for each channel you have registered.

I use this frequently in my server/client programs that have a number of modules that communicate across app-domains. Usually I create an IPC channel for exposing an object locally, and a TCP channel for exposing it globally.

Take for example an Alarm event server. The local app can receive events about alarms from a number of modules running on the server, and the client can view or acknowledge the alarms remotely.

The big thing to remember is that one request from one channel can block all activity (local and remote) if your operation takes a long time and is not set up to be asynchronous. You also have to keep in mind about reentrancy and concurency problems (like locking collections when they are modified).