NAM 1.0 NO IDEA Avatar
  1. OMG Issue

NAM — Alternate Protocol Specifications within URIs

  • Key: NAM-9
  • Legacy Issue Number: 2794
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Object URIs should accommodate multiple protocols. This is important for a
    wide range of present day systems, such as embedded and real-time systems
    that do not or cannot use TCP/IP, and will accommodate future expansion of
    CORBA beyond TCP/IP networks.

    Object URIs should

    • be extensible to allow additional addressing schemes for, at least, GIOPs
      over transports other than TCP/IP. A default of IIOP that results in a
      shorter form is allowable.
    • accommodate additional standardized addressing schemes as transports and
      protocols become adopted. (similar to that provided by the present IOR
      structure through the adoption of new standard profiles)
    • accommodate additional proprietary addressing schemes targeted for
      markets for which standardization might be inappropriate or too costly. In
      particular, it should allow assignment of partitions of the naming space to
      entities (similar to the current provision for vendor-specific profile tags)
  • Reported: NAM 1.0b1 — Thu, 8 Jul 1999 04:00 GMT
  • Disposition: Resolved — NAM 1.0
  • Disposition Summary:

    Support for multiple protocols is required. changed iioploc/iiopname to corbaloc/corbaname and chang

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