[omniORB] Object reference

[Renzo Tomaselli]

Andrew,
        just use the skeleton constructor which takes a key as a paramete=
r
(instead of accepting the default constructor which builds a random key).
That key for OmniORB is actually a long triplet; a good way I commonly us=
e
for building the same key value is to take a crc32 as a hash of the
Interface Repository ID of an interface. This solution has the nice side
effect of detecting version mismatch between actual implementation and ID=
L
definition. A bad side effect is to not allow for multiple instances of s=
uch
an object within the same address space.
It's a non-portable solution, but I think it can be easily adapted to oth=
er
ORBs since I expect anyone would accomodate space for 32 bits in an obj r=
ef
(assuming the other two triplet components are kept constant).
Hope this helps,
                                             Renzo Tomaselli
-------------------------------------------------------------------------=
--
TecnoTP s.n.c. Special Information System Design
Maso Pelauchi I38050 Ronchi Valsugana,  Trento TN  ITALY
Tel. +39 0461 773164      Fax. +39 0461 771514
e-mail: renzo.tomaselli@tecnotp.it
-------------------------------------------------------------------------=
--
-----Original Message-----
From: andrew.brown@bt.com <andrew.brown@bt.com>
To: omniorb-list@orl.co.uk <omniorb-list@orl.co.uk>
Date: luned=EC 22 febbraio 1999 18.38
Subject: [omniORB] Object reference


>Is it possible to pass exactly the same object reference from a server t=
o a
>client each time the server run's or to somehow define what the object
>reference is which is passed across. I want the client to be able to use=
 an
>object registered with the naming service, and for the client to use the
>same object reference even when the server has stopped and re-started.
>
>Thank you.
>
>Andrew Brown.
>
>