Groups | Blog | Home
all groups > dotnet remoting > march 2006 >

dotnet remoting : Configuring Multiple Clients of the Same Remote Object Type with Different URL Locations


jasonjoely NO[at]SPAM gmail.com
3/28/2006 1:56:58 PM
Hey,

Is it possible to have multiple clients of the same remote object type
but with different url locations? If so, how can this be setup?

I'm trying to use .net remoting for a current project of mine. Here's
a brief background:
The project will have a machine (which I'll refer to as the "Parent")
that oversees a number of other systems (which I'll refer to as the
"Kids"). The kids are basically a clone of each other. They perform
the same jobs/tasks. The parent system is then responsible for polling
each kid systems to ensure they are working properly and for prompting
the kids to do certain tasks whenever the need arises.

I want to use .net remoting as the means for the parent and all its
kids to communicate with each other. All the kids system will have the
same remote object type. The parent would then be the client to all
the different kids.

My questions is how do I set this up on the Parent system? From what I
could tell, the configuration file only allows you one url for a
specific remote object type.

Any help would be much appreciated. Thanks!

Jason
Momo
4/13/2006 3:43:02 PM
Jason,
Have you had any luck with this? I am having the exact issue that you
describe, however this is all that I am able to find.

http://www.thinktecture.com/Resources/RemotingFAQ/ACCESSING_SAME_TYPE.html

However I cannot seem to get this to work in my VB code. Traditional calls
using RegisterWellKnownClientType works fine for 1, however when I attempt to
call the code using the work around I now get a constructor error.

Matt

[quoted text, click to view]
AddThis Social Bookmark Button