Hi Breeto,
Indeed I didn't notice that you could add a "name" property to the
properties dictionary when registering the channel.
I noticed that there is also a property called "priority". I would think a
channel is chosen on the "priority" property. So a call or incoming call to a
remoted object would prefer the channel with the highest priority, unless the
channel is already being used by another call. But I must say that I'm
absolutely no expert at all, this is just a guess.
Other than that I would think that it is not important what channel is used,
but I could be wrong. I have no clear view on why you would want to assign a
specific channel for a specific remoted object.
This is just a guess, but would an extra AppDomain solve the issue? It
appears channels are bound to an AppDomain...
Regards,
--
Tom Tempelaere.
[quoted text, click to view] "breeto@yahoo.com" wrote:
> Yes, you can definitely register more than one channel of the same
> type. The only extra step you have to take is to give each channel a
> unique name. This can be easily done via RegisterChannel() overload or
> dictionary of channel properties.
>
> I'm still at loss though as to why they let you register multiple
> channels of the same type if they won't let you choose which channel to
> use for a given object proxy! I'm still hopeful there's a way, I'm
> just having a hard time finding it.
>
>
> TT (Tom Tempelaere) wrote:
> > Hi,
> >
> > I don't think you can register two channels of the same type. Have you ever
> > tried doing that?
> >
> > Kind regards,
> > --
> > Tom Tempelaere.
> >
> >
> > "breeto@yahoo.com" wrote:
> >
> > > If you've configured .NET Remoting to use more than one channel of the
> > > same type, for example two TcpClientChannels with unique names, when
> > > you want to create a proxy to a remote object how do you specify which
> > > channel you want that proxy to use?
> > >
> > > Thanks in advance.
> > >
> > >
>
