Browse Prior Art Database

Dynamic Object Capability Exchange

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

Publishing Venue

IBM

Related People

Breslau, FC: AUTHOR [+3]

Abstract

Disclosed is a 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.

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

Dynamic Object Capability Exchange

      Disclosed is a 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.

Two possible embodiments are considered:
  1.  A direct object-to-object protocol.
  2.  A centralized ORB/object protocol.

      In both embodiments certain meta-methods (i.e., those operating
on other methods within an object) are included.

      In this embodiment, each variable capability object informs
any others which have registered their interest about changes in it's
method's operability status.  Each variable capability object
provides a meta-method that can be invoked to query it's methods
operability, and a meta-method that can be invoked by other objects
to register as interested parties for updates.  In the later case
where objects register, the meta-method would poll the other methods
within it's object for operability.  The interested objects provide
meta-methods for the target variable capability objects to invoke for
notification of capability changes.

      Assume the Common Object Request Broker Architecture (CORBA)
distributed object architecture, with a central Object Request Broker
(ORB -- e.g., IBM* System Object Model (SOM) or Distributed System
Object Model (DSOM)).  Assume that two persistent objects (A and B)
are registered to the ORB, and that object A elicits functions from
object B, and object B possesses a variable set of capabilities.

Provide the following:
  o  A capability to denote a variable capability object as such at
      the time of registration by the ORB (or assume that all objects
      have variable capability sets); e.g., a bit in the registration
      entry that would be set to indicate that an object's
capabilities
      may change.
  o  A mechanism for registering an initial set of capabilities for
an
      object (the set to be kept by the ORB).
  o  A mechanism for updating an initial set of capabilities with a
      changed current set of capabilities for an object (to be
accepted
      by the ORB).
  o  A mechanism for an object to request a set of another object's
      capabilities from the ORB.

      It is also possible to extend the syntax of object programming
languages, such as C++, Smalltalk, or Object-Oriented COBOL to
provide built-in mechanisms for interrogation and exchange of object
capabilities.

The interactions would be as follows:
  o  Object A is created and registered to the ORB.
  o  Object B is created and registered to the ORB as a variable
      capability object.
  o  Upon creation, the initialization method of object B f...