[omniORB] Choosing specific end-points

[Wernke zur Borg]

Thanks @ Duncan for the IOP module. Certainly it would be possible to
unmarshal and remarshal the IORs sent to a client and put the correct IP
address in. But I think that's really ugly...

I am also not sure if I could make my initial problem clear to everybody.
I'll try to respond to Craig's post to clarify it.

Since my scheme of spawning dedicated client servers works (described in my
previous post) I would rather not touch it.

Thanks anyway
Wernke


> -----Original Message-----
> From: omniorb-list-bounces at omniorb-support.com 
> [mailto:omniorb-list-bounces at omniorb-support.com] On Behalf 
> Of Duncan Grisby
> Sent: 04 April 2005 18:19
> To: Wernke zur Borg
> Cc: omniorb-list at omniorb-support.com
> Subject: Re: [omniORB] Choosing specific end-points
> 
> On Monday 4 April, "Wernke zur Borg" wrote:
> 
> > I do not believe you can switch endpoints at runtime, 
> although I would love
> > to hear a different statement.
> 
> There is no API to do it, but it wouldn't be impossible (although it
> would be ugly) to add one.
> 
> In case you've missed it, it's possible to set the client's preference
> for particular endpoints using the clientTransportRule configuration
> parameter. That should be sufficient for many needs.
> 
> If you really do want to modify the endpoint order, an alternative to
> hacking the ORB is to unmarshal a stringified object reference into an
> IOR struct using the correct IDL definitions (which I've 
> attached). You
> can then modify the endpoints and remarshal it. I have Python 
> code that
> does that, except that it rewrites object keys rather than endpoints.
> 
> Cheers,
> 
> Duncan.
> 
>