OmniNames and bind_context

[Emmanuel Saint-Loubert]

Hello Gary,

> The interesting thing is that it actually does
> work, but the IOR that I bound is marked as nobject instead of
> ncontext.
>

Actually this is supposed to be the normal behavior. When you use bind
(instead of bind_context) your binding will always be to an object rather
than to a context. Because a context is also an object it is bound as such
in this case.

-- Emmanuel R. Saint-Loubert         saintlou@tumbleweed.com
   Tumbleweed Software Corp.       http://www.tumbleweed.com
   2010 Broadway                            Tel 650-569-3676
   Redwood City, CA 94063                   Fax 650-369-7197


Gary D. Duzan wrote:

>    I recently came across the case where I wanted to bind a context
> from one name server as a context in another. I went to try to do this
> using nameclt, but it didn't have a bind_context option, so I tried
> just using bind instead. The interesting thing is that it actually does
> work, but the IOR that I bound is marked as nobject instead of
> ncontext. This is not an ideal situation, of course, but at least it
> resolves names in it just like it was bound as a context.
>    I think it would be useful to have bind_context in nameclt for this
> sort of thing. Any chance of getting it into 2.4? (All this was with
> 2.2.) I don't know if adding external ncontext bindings would
> complicate OmniNames or not; I haven't looked at the code.
>
>                                         Gary Duzan
>                                         GTE Laboratories