[omniORB] Can I use a naming service with different orbs?

Mike Bendickson bendi003@tc.umn.edu
Tue, 31 Aug 1999 10:00:37 -0500


Oops, I wasn't clear.  I don't want to have to deal with IORs at all.  The
client configuration needs to consist of specifying a hostname and possibly
a port.  From that I want to be able to query for the IOR.  I think that
most orbs provide this, but as an extension (is this the Binder that you
mentioned?).  Forgive me, I'm new to all of this.  :)

So, am I out of luck?  Would LDAP be a good alternative?

Thanks,
-Mike

-----Original Message-----
From: Duncan Grisby <dgrisby@uk.research.att.com>
To: Mike Bendickson <bendi003@tc.umn.edu>
Cc: omniorb-list@uk.research.att.com <omniorb-list@uk.research.att.com>;
mico-devel@vsb.informatik.uni-frankfurt.de
<mico-devel@vsb.informatik.uni-frankfurt.de>
Date: Tuesday, August 31, 1999 9:39 AM
Subject: Re: [omniORB] Can I use a naming service with different orbs?


>On Tuesday 31 August, "Mike Bendickson" wrote:
>
>> We're using MICO on our Unix platform and omniORB2 on NT.  I read
somewhere
>> that the naming services are not compatible with each other.  Is this
>> correct?
>
>As long as MICO's naming service is fully compliant with the Naming
>service specification, you will be able to use it from omniORB, simply
>by putting its IOR in omniORB's configuration file. You won't be able
>to use omniORB's ORBinitialPort and ORBinitialHost configuration.
>
>omniORB's Naming service is fully compliant so, again, you should be
>able to use it from MICO. You can give omniORB's Naming service IOR to
>a MICO program with the -ORBNamingAddr command line argument.
>
>omniORB is not compatible with MICO's Binder mechanism, which is an
>extension to the CORBA spec.
>
>HTH,
>
>Duncan.
>
>--
> -- Duncan Grisby  \  Research Engineer  --
>  -- AT&T Laboratories Cambridge          --
>   -- http://www.uk.research.att.com/~dpg1 --
>
>