Browse Prior Art Database

Conversationally Dependent Multiple Task Termination

IP.com Disclosure Number: IPCOM000099744D
Original Publication Date: 1990-Feb-01
Included in the Prior Art Database: 2005-Mar-15
Document File: 2 page(s) / 80K

Publishing Venue

IBM

Related People

Franklin, SM: AUTHOR [+2]

Abstract

This article describes a method for applications to efficiently and securely terminate execution in an orderly fashion when these applications are dependently interconnected in each other's application processing. For example, such a relationship can occur when one application, called the client application, requires data from another independent application, called the server. The classic example for this model is a charting program receiving updates of data from a spreadsheet and reflecting those changes by redrawing the chart. In this case the charting program is the client and the spreadsheet is the server. A more sophisticated relationship can occur consisting of a N-way relationship between several applications.

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

Conversationally Dependent Multiple Task Termination

       This article describes a method for applications to
efficiently and securely terminate execution in an orderly fashion
when these applications are dependently interconnected in each
other's application processing.  For example, such a relationship can
occur when one application, called the client application, requires
data from another independent application, called the server.  The
classic example for this model is a charting program receiving
updates of data from a spreadsheet and reflecting those changes by
redrawing the chart.  In this case the charting program is the client
and the spreadsheet is the server.  A more sophisticated relationship
can occur consisting of a N-way relationship between several
applications. In an N-way conversation either the client or the
server or both applications may be involved in a one-to-many mode of
conversation.  That is, a single server may be supplying data to
multiple client applications or a client application may be receiving
data from several servers, or both.  Both the client applications,
which are dependent on server applications for the completeness and
integrity of their data, and server applications, which must be
sensitive to the data integrity and data requirements of their
clients, must be allowed to terminate their own execution when
required or requested.  Termination processing must be executed in
such a manner so that the application termination is accomplished so
that existing data dependencies are met and conversational
interconnectivity integrity between all participating applications is
maintained. Conversationally Dependent Multiple Task Termination
achieves both of these goals by providing a generic method for
terminating the conversational links between client and server
applications.

      Conversationally Dependent Multiple Task...