Issue 2942:  Interoperable Naming Service: Why no CosNaming::NamingContextExt: :bind_st                                                                                                                             (naming_ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: The INS (orbos/98-10-11) has a new method resolve_str to convert from a
StringName to an object in one step; the alternative would be to call
to_name (to convert a StringName to a Name) and then call resolve (to
convert the Name into an object reference).

Why isn't there a similar operation for bind, called bind_str: given a
StringName and an object reference, create the indicated binding.  The
current interface requires two method calls to create the binding.

Resolution: The submitters had considered a number of convenience operators but decline to add stringified versi
Revised Text:  CLOSED (No action required)
Actions taken:
September 23, 1999: received issue
May 4, 2000: closed issue
Discussion: 

End of Annotations:=====
Date: Thu, 23 Sep 1999 13:53:51 -0400
From: "Steele, Richard A" <Richard.Steele@usa.xerox.com>
Subject: Interoperable Naming Service: Why no
CosNaming::NamingContextExt:
 :bind_str?
To: "'issues@omg.org'" <issues@omg.org>
Message-id: 
 <DADB394AF196D211958700805F0DBA3101297F33@usa0875ms1.roch875.mc.xerox.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-transfer-encoding: 7BIT
Content-Type: text/plain; charset=iso-8859-1
X-UIDL: 1+R!!54Td9;?0!![T(e9


The INS (orbos/98-10-11) has a new method resolve_str to convert from
a
StringName to an object in one step; the alternative would be to call
to_name (to convert a StringName to a Name) and then call resolve (to
convert the Name into an object reference).

Why isn't there a similar operation for bind, called bind_str: given a
StringName and an object reference, create the indicated binding.  The
current interface requires two method calls to create the binding.

Richard A. Steele
Xerox Corporation