[omniORB] backup Naming Service

[jon.kristensen@kongsberg-simrad.com]

Hi,

we have a different, though similar problem.

We have one set of computers sitting in a surface ship and a second set of
computers in an underwater vehicle. Initially these computers are connected to
the same net, but when the underwater vehicle is deployed, the link to the
surface ship is disconnected. When the vehicle resurfaces, we want to reconnect.

We thus need two nameservices, one surface and one subsea. These must be
synchronized initially, and possibly also after the net is reconnected. Any
hints as to how to do this is most welcome.

We aslo have to detect when the link is disconnected. The obvious way is to
handle CORBA exceptions. Is there a better way?

Thanks for any help.

Best regards,
Jon Kristensen
Kongsberg Simrad AS, Horten Norway
phone:    +47 33 03 43 62
fax: +47 33 04 76 19
email:    jon.kristensen@kongsberg-simrad.com






Schuetz Andreas <Andreas.Schuetz@kst.siemens.de> on 07.10.99 14:00:39
To:   "'omniorb-list@uk.research.att.com'" <omniorb-list@uk.research.att.com>
cc:    (bcc: Jon Kristensen/NOHRT/KS/KM/KOG)
Subject:  [omniORB] backup Naming Service




Hi,

for a distributed application based on omniORB2, I use its Naming Service to
communicate object references between clients and servers. For a specific
project, it is required that the system continues working even if a computer
crashes. This raises the question how to provide something like a backup
Naming Service, if it's the computer running the Naming Service which fails.
Does anyone have experience with or has solved that kinds of problems?

Is it possible for an omniORB2 application to get an initial reference to an
alternate NS, if the one configured via ORBInitialHost/ORBInitialPort
doesn't respond?


Any help or comments welcome.



Andreas Schuetz
Siemens ElectroCom
78467 Konstanz, Germany