NAM 1.0 NO IDEA Avatar
  1. OMG Issue

NAM — Binding type "n_context":

  • Key: NAM-6
  • Legacy Issue Number: 2636
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: by using bind_context/rebind_context/bind_new_context versus those
    that are bound by using other means?

    If an application uses resolve() to lookup a naming context, it has no
    way of telling whether the naming context has the binding type
    n_context. In fact, it doesn"t care. So an application choosing to do
    piecewise resolution against CosNaming would see a different behavior
    than if it were to do whole resolution. This seems to contradict the
    subsection "Resolution of Compound Names" in Section 4.2, page 4-8. It
    seems that n_context is an implementation issue of CosNaming that is
    exposed to the application.

    The suggestion is to remove the third paragraph of the Usage section,
    or to change it so that n_context be set for any naming context bound
    in the namespace.

  • Reported: NAM 1.0b1 — Wed, 5 May 1999 04:00 GMT
  • Disposition: Resolved — NAM 1.0
  • Disposition Summary:

    Clarify role of when naming_contexts participate in name resolution, make text consistent with Usage

  • Updated: Fri, 6 Mar 2015 20:58 GMT