Browse Prior Art Database

Synchronization of Resource Access

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

Publishing Venue

IBM

Related People

Chapman, RA: AUTHOR

Abstract

In a multi-tasking environment with two or more applications accessing a non-shareable resource, it is possible that the applications will become disoriented with the resource if the resource is modified by one application while it is in use by another. Disclosed is a mechanism through which multiple applications can synchronize access to shared resources.

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

Synchronization of Resource Access

      In a multi-tasking environment with two or more applications
accessing a non-shareable resource, it is possible that the
applications will become disoriented with the resource if the
resource is modified by one application while it is in use by
another.  Disclosed is a mechanism through which multiple
applications can synchronize access to shared resources.

      A Resource Manager function is required whose responsibility it
is to manage application access to non-shareable resources.  These
resources can be files, communications ports, etc.  As resources are
identified, the Resource Manager is notified and defines the resource
in an internal resource pool.  Each application must query the
Resource Manager to gain access to the resource.  The Resource
Manager then responds to the application's resource request.

      If the request is accepted, the resource is available and
checked out to the application.  While the application is checked
out, the Resource Manager will prevent other applications from
accessing the resource.

      If the request is rejected, the resource is already in use or
checked out, in which case the request is queued and the application
is notified when the resource becomes available.  The rejection
notification also returns the ID of the application owning the
resource to allow the applications to communicate.  This allows
applications to "discuss" the rights of the resource.  The en...