Summary by Uma Jaipradeep  
Implementation by Prasad Joshi
 
 

The information presented was gathered from Internet. 

Summary Contents

Naming Service Overview

Naming Objects in the Distributed Object System

Naming Contexts

Object Names

Binding an Object with a Name

Resolving a Named Object

Creating a New naming Context

Listing the Contents of a Naming Context

Unbinding an Object from a Naming Context

Client-Server Naming Scenario

Implementation of Naming Service

Links

Naming Objects in the Distributed Object System

Business objects and other resources can be assigned a name in the system name space. This is called binding an object. After you bind an object with a name you can find that object or resolve it by its name.

Binding an object has several advantages. Most notably it provides end-users and programmers a way to talk about particular objects. Names essentially form human-identities for objects. These names can be passed between people and their programs either through user interfaces or in program code.

The name service has these primary uses for locating: 

• System resources, including collections of business objects. 
• Business objects grouped in application naming contexts. 

In both instances, the naming service is used to form an enterprise-wide(or at least workgroup-wide) name space from which named objects can be reliably found.

A fundamental concept in the Component Broker naming service is that the entire name space is composed of objects bound in one or more naming contexts. Each naming context is itself an object and can be bound to other naming contexts to form a tree. In this fashion, the name space can be structured into a hierarchy of names. Any object then has both a relative name, their name within a naming context, and a compound name, the name path representing a particular traversal through the name hierarchy from a higher-level naming context to that object. 

To further exemplify the placement of objects and naming contexts in the name tree consider the name tree depicted in the diagram that follows. This name tree is composed of a hierarchy of naming contexts and objects (naming contexts contain other naming contexts and/or objects). Notice that only the object bindings have names and not the objects themselves. Thus an object name is by its very nature contextual. The name of an object only exists within a given context, and then only if the object is bound to that context. The context at the top of the tree does not have a name at all (by virtue of not being bound to any other context). This document refers to this as the root of the tree. 

Summary Contents

Naming Service Overview

Naming Objects in the Distributed Object System

Naming Contexts

Object Names

Binding an Object with a Name

Resolving a Named Object

Creating a New naming Context

Listing the Contents of a Naming Context

Unbinding an Object from a Naming Context

Client-Server Naming Scenario

Implementation of Naming Service

Links