Browse Prior Art Database

Persistent Framework Independent Record/Playback Framework

IP.com Disclosure Number: IPCOM000104880D
Original Publication Date: 1993-Jun-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 4 page(s) / 151K

Publishing Venue

IBM

Related People

Coskun, N: AUTHOR

Abstract

Name Lookup technique, offered by the System Object Model (SOM), can be used to design a record/playback framework in a persistent framework independent way. The design of record/playback will document the signature of the persistent framework interfaces that are used. So, any persistent framework supporting the interfaces with the given signature can be used with the record/playback framework.

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

Persistent Framework Independent Record/Playback Framework

      Name Lookup technique, offered by the System Object Model
(SOM), can be used to design a record/playback framework in a
persistent framework independent way.  The design of record/playback
will document the signature of the persistent framework interfaces
that are used.  So, any persistent framework supporting the
interfaces with the given signature can be used with the
record/playback framework.

      An application framework is a collection of frameworks which
simplifies application development.  This simplification is achieved
through call libraries and/or framework, which provide reuseable code
to the application framework code and addes new features through
specialization of the framework classes.

      One of the desirable frameworks in an application framework is
a record/playback framework.  The purpose of a record/playback
framework is to provide the ability to record and playback method
calls.  This type of functionally is a requirement in various areas
in an application framework.  Some of the possible applications are
undo, extension language support, persistent framework and
replication framework.

      In a replication framework, one of the requirements is to
create an external representation for method calls that can be
transferred to a remote host or another process.  The receiver of
such and external representation then would like to reconstruct the
method call from the external representation and execute the command.
In other words, all the information about the method calls, such as
target object, method name, and its arguments, should be suitable to
externalize it.  Externalizing method names and primitive data types,
like integer, real, character and strings, is straight forward.
Another data type that is in common use in an application framework
is object data type.  Objects can be classified as persistent and
nonpersistent.  Both persistent and nonpersistent objects have ids
that can be retrieved from the persistent framework which is used by
the application framework.  Given an id, it is possible to request an
object from the persistent framework.  In other words external
representations of the objects are the persistent-framework supported
ids.  Given such an id, the persistent framework also provides the
corresponding object.  In other words, record/playback framework
needs to communicate with the persistent framework to externalize and
internalize the object arguments.  This type of communication can be
done in a persistent framework independent way.  This article
describles an algorithm that achieves implementation of a
persistent-framework independent record/playback framework.

      System Object Model (SOM) provides two kinds of method
resolutions.

1.  Static method resolution, which depends on the class hierarchy of
    the method, is the only type of method resolution offered by
    popular object-o...