[omniORB] persistent object references

[Alex Tingle]

OmniEvents stores its port in a file, and then initialises the ORB like 
this:

   char endPoint[64];
   sprintf(endPoint,"giop:::%d",port);
   const char* opts[][2] ={ {"endPoint",endPoint}, {0,0} };
   orb=CORBA::ORB_init(argc,argv,"omniORB4",opts);

-Alex

--
Dammit Jim, I'm a programmer... not a mind reader!
On 23 Aug 2004, at 15:12, Ahlborn, James T (MED) wrote:

> hey,
> i'm trying to get persistent object references working with omniorb 
> and i'm
> just wondering how others out there are doing it.  obviously, omniorb 
> does
> not have an ImR (although it seems someone posted a simple one a while 
> ago).
> The only (partial) solution i've seen so far is forcing a server to 
> use the
> same port each time and to use the USERID policy in the POA, which will
> cause the orb to generate identical IORs on each run.  however, this 
> suffers
> from annoying configuration issues, where each server process needs to 
> be
> assiged a unique port number by some config file somewhere.  has 
> anyone out
> there come up with a more general solution?  i don't need the full 
> power of
> an ImR to start objects on demand, i just want objects to have 
> repeatable
> IORs.  is there a good general way to pass out port numbers?  or 
> possibly
> force them to be persisted in a log file (i guess that's what the
> nameservice and eventservice do)?
> thoughts?
> -james
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list