Why naming service in corba

Order can be used to locate the Order object. A CosNaming::Name data structure is not simply a string of alphanumeric characters; it is a sequence of one or more CosNaming::NameComponent data structures. Each CosNaming::NameComponent data structure contains two strings, id and kind. The net effect is that the IDL definitions for the Naming Service have a useless typedef definition, which confuses some people.

In order to allow support for foo. The resulting definition of a hierarchical name is shown below:. The result is certainly flexible, but it is also over-engineered. Most people do not need all this flexibility and become frustrated with the complexity that it introduces to their applications. The developers of such an application have to write their own function to convert the string into the CosNaming :: Name format. One problem is that it is a waste of time for numerous developers in different organizations around the world to re-invent the wheel in writing such a utility function.

Another problem is that each of these developers must choose what hierarchical separator they want and the separator between the id and kind fields of NameComponent. Hindsight is a wonderful thing, and a few years later the OMG decided to simplify the complexity of hierarchical names by defining a new version of the Naming Service.

As I will discuss in Section 9. However, there is no similar utility operation defined for the bind or rebind operations that servers use to advertise an IOR in the Naming Service. The final area of potential confusion for developers is the list operation, which is illustrated in Figure 4. An out parameter of this operation provides a non-recursive listing of the entries in a naming context. CTM daemons exchange information with each other, including information about the business-processing programs on other hosts.

Note that a failure has occurred on host A. The illustrated application organizes its namespace by geographic region, then by department. A NamingContext object contains a list of CosNaming::Name data structures that have been bound to application objects or to other NamingContext objects.

NamingContext objects are traversed to locate a particular name. For example, the logical name California.