Issue 5926: Binding a Stringified Name (naming_ftf)
Source: Zuehlke Engineering (Mr. Frank Pilhofer, fpilhofer2008(at)gmail.com)
Nature: Uncategorized Issue
Severity: 
Summary: The NamingContextExt interface has a resolve_str
operation that takes a string and returns its
binding.


I suggest to add a converse bind_str operation:


  void bind_str (in StringName sn, in Object obj)
    raises (NotFound, CannotProceed, InvalidName,
            AlreadyBound);


That would allow not only lightweight clients to
use the Naming Service, but also lightweight servers
to publish their references as easily as possible.


(And a Lightweight Naming Service would be possible
that just implemented these two operations.)

Resolution: 
Revised Text: 
Actions taken:
May 2, 2003: received issue
Discussion: 

End of Annotations:=====
Subject: Binding a Stringified Name 
Date: Fri, 2 May 2003 09:20:47 -0400 
Thread-Topic: Binding a Stringified Name 
Thread-Index: AcMQraRUD9qgKT/NTtyXNvY7b4idTg== 
From: "Pilhofer, Frank" <fpilhofe@mc.com> 
To: <naming_ftf@omg.org>, <issues@omg.org> 
X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h42DMeeK008878 


This is a new issue for the Naming FTF/RTF.
Hope somebody is listening here.


The NamingContextExt interface has a resolve_str
operation that takes a string and returns its
binding.


I suggest to add a converse bind_str operation:


  void bind_str (in StringName sn, in Object obj)
    raises (NotFound, CannotProceed, InvalidName,
            AlreadyBound);


That would allow not only lightweight clients to
use the Naming Service, but also lightweight servers
to publish their references as easily as possible.


(And a Lightweight Naming Service would be possible
that just implemented these two operations.)

Frank