[omniORB] corbaloc for unix and SSL endpoints

[Bastiaan Bakker]

> -----Original Message-----
> From: Duncan Grisby [mailto:dgrisby@uk.research.att.com]
> Sent: Wednesday, February 20, 2002 1:09 PM
> To: Bastiaan Bakker
> Cc: omniORB-list (E-mail) (E-mail)
> Subject: Re: [omniORB] corbaloc for unix and SSL endpoints=20
>=20
>=20
> On Friday 8 February, "Bastiaan Bakker" wrote:
>=20
> > While browsing the documentation for the 'corbaloc' syntax,=20
> I noticed
> > that currently it's not possible to denote a reference to a=20
> CORBA object
> > listening on a Unix domain or SSL socket. I imagine that=20
> they would be
> > something like:
> > corbaloc:uiop:\/tmp\/omni.socket/object  and
> > corbaloc:iiops:server.example.com:1443/object
>=20
> I don't think there should be a corbaloc format for the Unix domain
> transport, since it is omniORB specific. corbaloc should only be used
> for getting hold of a small number of initial references, which are
> then used to get other object references. If a server supports the
> Unix transport, object references acquired from it will include
> information about the Unix endpoint.

Well, one the reasons why I want a corbaloc for Unix domain transport is =
to access the Naming Service through Unix sockets. (Call me a sick =
bastard, but ya aint gonnna stop me :-)
I could use IOR format, but that's ugly and messy.
BTW is there any reason why Unix transport should be omniORB specific? =
AFAICS is just a way to create a bit pipe to another ORB. I don't know =
how for example ORBit handles Unix transport, but it would be nice to be =
able to interoperate. =20

>=20
> The SSL transport is slightly different, in that it will be common for
> a server to only be contactable by SSL. In the absence of a standard
> protocol name for it, I would suggest naming the protocol omnissl or
> something like that, to make it obvious that the format is
> non-portable.

OK, I'll prefix both with omni.
=20
> It should be pretty easy to add a new protocol to the corbaloc parser.
> If you want to give it a go, look at uri.cc and ior.cc.

I've started browsing the code this weekend. Adding the protocols to the =
parser looks simple enough. But I'm unsure how to create the omniIOR =
with the necessary Profiles. A marshal method for the UNIX_TRANS tag =
does not seem to be available.
Any hints would be appreciated.

Cheers,

Bastiaan

=20