Browse Prior Art Database

OS/2 Thread Usage for Capturing/Replaying Presentation Manager Data

IP.com Disclosure Number: IPCOM000102635D
Original Publication Date: 1990-Dec-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 1 page(s) / 37K

Publishing Venue

IBM

Related People

Baird, JM: AUTHOR [+3]

Abstract

This article describes a method for using OS/2* thread management to capture Presentation Manager* (PM) data. Later, this captured data can be replayed using the same thread management.

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

OS/2 Thread Usage for Capturing/Replaying Presentation Manager Data

       This article describes a method for using OS/2* thread
management to capture Presentation Manager* (PM) data. Later, this
captured data can be replayed using the same thread management.

      The capturing of the data is done by allocating three threads:
two for the capturing of keyboard and mouse data, and one for the
writing of the data to a file.  The capture threads record the user's
keyboard and mouse input and then pass the data off to the file I/O
thread.  Because this data is time-stamped and put on a queue, the
file I/O thread has the ability to keep track of the timing of the
user's input.

      The replay of the data is also performed by allocating three
threads: two for the replaying of the keyboard and mouse data, and
one for the writing of the data to a file. The file I/O thread reads
the output file from the capture and uses the time stamps to let the
keyboard and mouse threads know when to re-execute the original user
input.

      The following figure helps to illustrate how these threads
interact:

      The capturing of the data is performed by the left and center
sides of the figure.  The replay is done at a later time by the
center and right sides of the figure.  The captured data is written
to the file, and then later read back for the replay function. *
Trademark of IBM Corp.