Browse Prior Art Database

Asynchronous Process Communication Procedure

IP.com Disclosure Number: IPCOM000117592D
Original Publication Date: 1996-Apr-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 57K

Publishing Venue

IBM

Related People

Lennon, CJ: AUTHOR [+3]

Abstract

Disclosed is a methodology for passing data between two Operating System/2 (OS/2*) processes in a completely asynchronous manner. This methodology does not require the receiving process to be active at the time data is sent.

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

Asynchronous Process Communication Procedure

      Disclosed is a methodology for passing data between two
Operating System/2 (OS/2*) processes in a completely asynchronous
manner.  This methodology does not require the receiving process to
be active at the time data is sent.

      This methodology uses a background daemon that facilitates the
asynchronous transfer of data and a data transfer Dynamic Link
Library (DLL) program containing the Application Program Interfaces
(APIs) to be used by both the sending and receiving application.  The
background daemon has two (APIs): send_data() and get_data().  The
send_data() API requires three parameters: the address of the data
to be sent, data length, and a data Identification (ID) value through
which the data is labeled.  The get_data() API has the same three
parameters used to receive data.

      When data is to be sent to another process or application,
the sender loads the data_transfer DLL and calls its API (that is,
send_data()).  The DLL allocates a memory area using the length
passed on the API and copies the data from the caller's buffer into
the newly acquired data area and holds a copy of the data ID value
also passed on the call.  Control is returned to the caller and this
data area is then converted to shared memory using the DosGiveSeg()
call.  The shared memory area is set to a user count of one and its
address and the data ID value are placed on a queue that will be
processed by the backgroun...