Browse Prior Art Database

PROPAGATION OF IDENTITY THROUGHOUT OBJECT CLIQUES

IP.com Disclosure Number: IPCOM000013481D
Original Publication Date: 2001-May-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 2 page(s) / 73K

Publishing Venue

IBM

Abstract

Disclosed is a mechanism that allows identity (or key) information to be shared among groups of related Objects in an Object Oriented Programming model. This sharing is performed in such a way so as to insolate the programmer from knowledge and management of the related objects. For the purposes of this discussion, such groups of related objects will be referred to as cliques. In groups of related objects cliques in which those objects have a relationship with persistent data, the sharing of key information among those objects can become necessary. A prime example of this is in the Naming Service in the CORBA programming model. The CORBA Naming Service CosNaming module identifies a number of classes including the NamingContext and BindingIterator classes. Each instance of a BindingIterator has an association with a single NamingContext .

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

PROPAGATION OF IDENTITY THROUGHOUT OBJECT CLIQUES

Disclosed is a mechanism that allows identity (or key) information to be shared among groups of related Objects in an Object Oriented Programming model. This sharing is performed in such a way so as to insolate the programmer from knowledge and management of the related objects. For the purposes of this discussion, such groups of related objects will be referred to as cliques. In groups of related objects cliques in which those objects have a relationship with persistent data, the sharing of key information among those objects can become necessary. A prime example of this is in the Naming Service in the CORBA programming model. The CORBA Naming Service CosNaming module identifies a number of classes including the NamingContext and BindingIterator classes. Each instance of a BindingIterator has an association with a single NamingContext.

A NamingContext contains bindings to other objects which may include other NamingContexts or application objects. Thus, graphs of NamingContext can be created to construct a system Name Space. Each NamingContext supports the list method, which can be used to obtain a list of all of its bindings. (Refer to the Object Management Group's CORBAServices specification for further information on the Naming Service.)

The list method returns an initial set of bindings as well as a BindingIterator that can be used by the caller to retrieve the remaining bindings. Thus, the BindingIterator and NamingContext form what will be termed here an object clique. When the BindingIterator is created, it must obtain the necessary information to search the underlying directory (or other persistent store) for the bindings of its associated NamingContext . The problem solved by this invention is how to provide this information to the BindingIterator without introducing additional method interfaces on that BindingIterator . The solution will be to propagate the identity of the NamingContext to the BindingIterator.

The invention propagates the identity of the NamingContext into the BindingIterator via the following processing in the list method:

void list(in unsigned long how_many,
out BindingList bl,
out BindingIterator bi)
raises(BAD_PAR...