Browse Prior Art Database

Architecture Design for Component Separation of Client/Server Applications

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

Publishing Venue

IBM

Related People

Jefferson, KJ: AUTHOR [+3]

Abstract

Described is an architecture for designing client/server application which is based on the separation of the application into three distinct pieces:

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

Architecture Design for Component Separation of Client/Server Applications

      Described is an architecture for designing client/server
application which is based on the separation of the application into
three distinct pieces:

o   The end user interface (EUI)

o   Data exchange and communications

o   Data control and storage

      These applications should be written with an emphasis on the
use of generalized function to promote code reuse.  They should also
be written to exploit the operating environment and its facilities to
achieve the best end user perceived performance.

      The remaining part of this article will explain what these
components are and how they are used.

      STRUCTURE OF THE CLIENT: The client side of an application can
be broken down into three basic parts.

o   The end user interface (EUI)

o   The environment or programming interface (API)

o   The communication processor

      The application EUI portion of each application contains the
logic that control the "look and feel" of the application to the
user.  This logic is specific to each application and involves the
issuing of standard operation system APIs and the use of any other
application specific facilities.  It should be written so that all
issues for data are done via a set of "application" API's.  These
API's reside in the environment interface and force the EUI to
function like a client/server application to the environment
interface.

      The environment interface is the section of code that serves as
an in-storage library for the application.  It is accessible from the
application EUI.  The environment interface maps the application
function (available via API) to the server's data control and storage
and is, therefore, specific to the server's database structure and
environment.  The application EUI requests service of the environment
interface through a standard calling interface or API.  The
environment interface returns the results of that request to the
calling EUI.  To accommodate other server database structures and
environments, only specific EUI service request interfaces effected
by a change in the data control and service environment would have to
be changed.  In this way, the client side of the application can
easily be changed to integrate with products that were not in its
original design.  As long as the result of the effected EUI
interfaces is in the format expected by the EUI, these changes can be
made without effecting the EUI portion of the application.

      The communication processor is the process that controls the
communications from the client side of the application or the
requests to the data server machine.  The communications processor
used standard communication protocols to pass requests to the data
server machine (i.e.  NetBIOS, TCP/IP, APPC, ...).  The
communications processor can be changed to accommodate other
communication protocols, such as LU6.2 or LU2, wi...