Browse Prior Art Database

Implementation of a Client Supporting N Communication Systems

IP.com Disclosure Number: IPCOM000118868D
Original Publication Date: 1997-Aug-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 2 page(s) / 71K

Publishing Venue

IBM

Related People

Hlava, A: AUTHOR

Abstract

Disclosed is a method for creating a single client executable which can communicate using any of a set of different communication systems, such as Distributed Computer Environment (DCE), sockets, etc.

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

Implementation of a Client Supporting N Communication Systems

      Disclosed is a method for creating a single client executable
which can communicate using any of a set of different communication
systems, such as Distributed Computer Environment (DCE), sockets,
etc.

      The disclosed solution is an object-oriented communication
system class hierarchy coupled with a "successor chain" of
communication system object instances.  The class hierarchy provides
a way of encapsulating details of the communication system(s) from
the other code  in the application.  The successor chain and the
associated logic for traversing it provide the mechanism for
supporting N (where N is 1 or more) communication systems in one
client executable.

The communication system class hierarchy can be illustrated as
follows:
                  CommunicationSystem
                      |
                      |
                      A
                      |
                      |---(sublcass) ABCCommunicationSystem
                      |
                      |---(sublcass) XYZCommunicationSystem
                      .
                      .
                      .

      CommunicationSystem is a class which presents an abstract,
virtual communication system interface to the rest of the
application.  It is independent of the actual communication system(s)
in use by the client/server application.  The CommunicationSystem
subclasses contain the concrete implementations of this abstract
interface.  For example, one might implement the abstract interface
using DCE while another could implement it using standard internet
sockets.

      The CommunicationSystem base class contains a pointer to a
"successor" communication system and logic for traversing the chain
of successors according to the function being requested.  The actual
communication systems are arranged in precedence order on the chain.
Thus, a client which supports both the ABC and XYZ communication
systems (in that order) would have an object instance successor chain
like the following:
                       +------------------------+
  p_comm_sys --------> | ABCCommunicationSystem |
                       |------------------------|
                       | p_successor *     ...