Browse Prior Art Database

Request/Resume Commands With Intervening Gets/Sets

IP.com Disclosure Number: IPCOM000120286D
Original Publication Date: 1991-Mar-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 59K

Publishing Venue

IBM

Related People

Dunn, JC: AUTHOR [+2]

Abstract

Software systems with programming interfaces frequently allow user prototyping or customization tools. User developed prototypes or applications that use these tools are highly modal. Most APIs use some form of call-return interface. This design falls short when the service application (SA) has some unexpected need to request information from the calling application (CA). More specifically, if the SA is in some modal state which makes exiting to the CA inconvenient or impossible, the current call- return model is not adequate.

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

Request/Resume Commands With Intervening Gets/Sets

      Software systems with programming interfaces frequently allow
user prototyping or customization tools.  User developed prototypes
or applications that use these tools are highly modal.  Most APIs use
some form of call-return interface.  This design falls short when the
service application (SA) has some unexpected need to request
information from the calling application (CA).  More specifically, if
the SA is in some modal state which makes exiting to the CA
inconvenient or impossible, the current call- return model is not
adequate.

      Disclosed is a protocol that solves this problem by introducing
Request/Resume commands to the existing Call-Return interface.  The
'REQUEST' and 'RESUME' commands will have the following
characteristics:
  REQUEST is to be issued from the SA to initiate a request from the
CA.  The SA suspends processing until the CA returns. The current
host environment remains unchanged.  When a REQUEST command is
issued, the CA begins to process the request. The SA is temporarily
frozen.
  RESUME is to be issued from the CA after it has finished processing
the REQUEST.  When a RESUME is issued, the SA host returns to its
state immediately before the corresponding REQUEST.
  Between REQUEST and RESUME commands, communication between the CA
and the SA is intentionally limited.  This is necessary to preserve
the state of the host.  However, the CA can issue 'data passing
commands'...