Browse Prior Art Database

Dynamic Object Capability Exchange using a Dependency Graph

IP.com Disclosure Number: IPCOM000117492D
Original Publication Date: 1996-Mar-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 81K

Publishing Venue

IBM

Related People

Breslau, FC: AUTHOR [+3]

Abstract

Disclosed is a method for Improvement to the dynamic object capability exchange mechanism making use of a centralized dependency graph to reduce the number of interactions required to communicate a capability change of an object.

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

Dynamic Object Capability Exchange using a Dependency Graph

      Disclosed is a method for Improvement to the dynamic object
capability exchange mechanism making use of a centralized dependency
graph to reduce the number of interactions required to communicate a
capability change of an object.

      Disclosed is an improvement to the mechanism for dynamic
communication of changing capability of programming objects to
interested parties with the intention of determining the mutual
capability of a set of objects.  The improvement makes use of a
centralized dependency graph to reduce the number of interactions for
communication of a change in an object's capability and makes the
overall common capability set determination faster by eliminating
staged capability updates.

      In a distributed object environment, e.g., Common Object
Request Broker Architecture (CORBA) as embodied by the IBM* System
Object Model (SOM) or Distributed System Object Model (DSOM),
communications of changed object capabilities with respect to
availability of methods within objects are performed via the
centralized Object Request Broker (ORB).  In addition to registering
their changing capabilities with the ORB, the variable-capability
objects and the interested parties (i.e., other objects that are
making use of methods within variable-capability objects) may
indicate to ORB their dependencies on particular capabilities of
particular objects.  This information may be provided at the time of
object registration, e.g., in the form of dependency list -- i.e.,
when object X is created, it may indicate to the ORB at the time of
registration that its method X1 availability is dependent on the
availability of method Y2 of object Y.  The ORB, being the central
repository of this dependency information will build a dependency
graph of variable capabilities within the object environment.  When a
particular method within a particular object becomes unavailable, the
ORB, using this dependency graph, will be able to immediately
determine all the effects...