[omniORB] Securing a Name Service

[JohnD.Heintz]

On Friday 29 June 2001 10:58, Duncan Grisby wrote:
> On Friday 29 June, John D. Heintz wrote:
> > I've found the docs for omniINSPOA and would like to know if I can:
> > 1) use corbaloc: syntax to directly refer to objects created on this
> > POA?  I think this is directly implied by the docs)
>
> Yes. You also have to be careful to always use the same TCP port
> number for your server, with the -ORBpoa_iiop_port command line
> argument.

Right, I got that.

>
> > 2) use children of omniINSPOA the same way?  (Do they have the same
> > property regarding object keys?)  I may want to specify threading
> > policies for example.
>
> No. Data is needed in the object key to tell the ORB which POA an
> object belongs to. There can be only one POA exempt from this, and
> that's the INS POA.

Ahh, that makes sense.  What are the rest of the policies for omniINSPOA =
then?

>
> > If I can just use corbaloc: I really don't even need a NameService do=
 I?
>
> Maybe not. It all depends how many objects you need to publish to the
> outside world, and if you need the extra functions of the Naming
> service like being able to list the contents.

Just one, so we should be all set.

Thanks,
John

>
> Cheers,
>
> Duncan.

--=20
=2E . . . . . . . . . . . . . . . . . . . . . . .

John D. Heintz | Senior Engineer

1016 La Posada Dr. | Suite 240 | Austin TX 78752
T 512.633.1198 | jheintz@isogen.com

w w w . d a t a c h a n n e l . c o m