Browse Prior Art Database

Packaging Methodology for Enabling of Future Enhancements

IP.com Disclosure Number: IPCOM000099261D
Original Publication Date: 1990-Jan-01
Included in the Prior Art Database: 2005-Mar-14
Document File: 2 page(s) / 74K

Publishing Venue

IBM

Related People

Elliott, LC: AUTHOR [+3]

Abstract

This article describes a packaging design which for enhancements with a minimal impact to existing This design should also be efficient in its memory

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

Packaging Methodology for Enabling of Future Enhancements

       This article describes a packaging design which for
enhancements with a minimal impact to existing  This design should
also be efficient in its memory

      Remote Data Services provides the interface between
applications and the remote databases which they  A high level
protocol (HLP) is used to control the of the data which is
transmitted between the and the database.

      HLP like all protocols is subject to change.  As environments
change, so will the protocols which those environments.  It is
optimal that as much as of the code that supports the protocols be
shielded these changes.  This was an important consideration in
design of Remote Data Services.

      By isolating the protocol rules and flows into tables,
supporting code is somewhat shielded from modifications the protocol.
 The tables were designed with allowances future enhancements so that
they could be extendable.

      The data which could not be broken down into table form into
three categories.  The first is the code which the information in the
tables to construct data for transmitting database kernel requests.
The type is logic which is architecturally controlled, could not be
reduced into a table (e.g., that which additional information
supplied only at execution  The third category is the set of protocol
rules cannot be efficiently implemented through tables.

      The code which supports the tables was designed so that is
dependent on the structure of the tables, but is of the data within
them.  This allows it to be from protocol constraints.  This code is
referred as static code because it should not normally be modified
the protocol evolves.

      The second and third types of data result in code which
reflects the protocol guidelines.  This code is to as dynamic code
because it is expected t...