NAM 1.0 NO IDEA Avatar
  1. OMG Issue

NAM — Unclear requirements for support of textual object keys

  • Key: NAM-11
  • Legacy Issue Number: 2899
  • Status: closed  
  • Source: Cisco Systems ( Paul Kyzivat)
  • Summary:

    The core changes introduced by the adoption of the INS specification
    have provided the means for a client to fabricate an object reference
    with a key containing arbitrary octets, and designating any server

    This is the first time that an OMG specification has violated the rule
    that object keys are opaque, formatted at the discretion of the server
    orb. This rule is violated because, at a minimum, the changes seem to
    require that a key containing the characters "NameService" must be a
    valid key in some server in order to support the INS specification.

    It seems that CORBA is now requiring that a conforming orb must natively
    support at least some range of text-like keys, either in all servers or
    in at least one specially constructed server.

    If this is indeed a requirement, then there is a need to spell out
    clearly the extent of this requirement:

  • Reported: NAM 1.0b1 — Tue, 5 Oct 1999 04:00 GMT
  • Disposition: Closed; No Change — NAM 1.0
  • Disposition Summary:

    The INS specification is not specifying server side behavior.

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