Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Reusable Object Oriented Framework for Plug Compatible Applications

IP.com Disclosure Number: IPCOM000115192D
Original Publication Date: 1995-Mar-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 8 page(s) / 315K

Publishing Venue

IBM

Related People

Austvold, SM: AUTHOR [+8]

Abstract

A reusable Object Oriented (OO) framework for plug compatible application development is disclosed. Object oriented techniques are put to use for an extendible, multiprocessing framework suitable for a local or distributed computing environment. The concept of client and server objects give meaning to the client/server application development.

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

Reusable Object Oriented Framework for Plug Compatible Applications

      A reusable Object Oriented (OO) framework for plug compatible
application development is disclosed.  Object oriented techniques are
put to use for an extendible, multiprocessing framework suitable for
a local or distributed computing environment.  The concept of client
and server objects give meaning to the client/server application
development.

      This framework provides a general solution for cooperative
asynchronous processes across multiple "sockets" in a network.  This
means that there can be from 1 to n processes running at the same
time where n is limited by the maximum number of processes that the
operating system can accommodate.  These processes could likewise be
distributed across many processors or a distributed computing
environment.  The framework is flexible enough to handle single or
multiple processes and processors.

Note: The term "socket" is used throughout this publication in the
general sense of the term.  It is by no means to be confused with the
particular communication mechanism common to the unix or
client/server computing paradigm.  It is simply a receiver of packets
of work.  For the specific definition see the section on "Sockets."

      The main objective was to design an object oriented,
dynamically extensible, reusable architecture for navigation through
a user interface.  At the same time, be architected general enough to
suit applications that have no user interface or that have other
additional requirements.

      One of these requirements might be the ability for applications
that are written using this framework to communicate with each other
in a natural and seamless way.  This is the idea of "plug compatible"
applications.  This ability allows one application to call a subset
of the function provided by another application without requiring a
new Application Program Interface (API).

      The OO solution follows a client/server theme where there are
client objects that request information and server objects that
process information.  The following points sum up the interaction of
these objects:
  o  Client has one specific task or work item it is responsible for.
  o  Client must gather the required information from one or several
      servers.
  o  Server processes the requested task and returns desired
      information.
  o  Client interprets results and must take appropriate action.
This
      action might be to create a new client (child) or return to a
      previous client (parent).
  o  Clients become a chain of modular work units that have a
      parent-child relationship.
  o  When the original client's role is accomplished the application
      is complete.

      The architecture centers around very powerful objects called
WorkUnits.  They contain the logic to interact and cooperate with
other agents in the network for the system to...