Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Reserved-Checkout for Versioned Object

IP.com Disclosure Number: IPCOM000104226D
Original Publication Date: 1993-Mar-01
Included in the Prior Art Database: 2005-Mar-18
Document File: 2 page(s) / 81K

Publishing Venue

IBM

Related People

Lin, DH: AUTHOR [+3]

Abstract

Version control is one of the most important functions in various data-intensive application domains, such as software engineering, CAD/CAM systems and office information systems dealing with compound documents. Normally, users use the "Checkout" command to check out data objects. However, it is very inconvenient for the user to check out objects which has been checked out by somebody else. The user has to keep trying until these objects are available. This disclosure proposes a reserved check out scheme so that all the reserved check out requests will be kept in a reservation queue. The user will get the data object as soon as it is available. The proposed scheme also sends reminder to people who checked out objects.

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

Reserved-Checkout for Versioned Object

      Version control is one of the most important functions in
various data-intensive application domains, such as software
engineering, CAD/CAM systems and office information systems dealing
with compound documents.  Normally, users use the "Checkout" command
to check out data objects.  However, it is very inconvenient for the
user to check out objects which has been checked out by somebody
else.  The user has to keep trying until these objects are available.
This disclosure proposes a reserved check out scheme so that all the
reserved check out requests will be kept in a reservation queue.  The
user will get the data object as soon as it is available.  The
proposed scheme also sends reminder to people who checked out
objects.

      In the versioned control object environment [*], users can
declare objects to be either versioned or non-versioned object.
Users need to use "Checkout" and "Checkin" commands  provided by the
version manager to access versioned objects.  Users are not allowed
to change the contents of currently existing versions.  A new version
will be created from the existing version whenever it is being
updated.  The version manager keeps track of the version derivation
hierarchy.  When a user uses a "Checkout" command to check out a
versioned object, the version manager will create a transient sient
version for the user.  All updates will be applied to this transient
object.  However, the user might not want the parent object to be
checked out by anyone else.  Users can issue a "LockParent" command
to obtain exclusive lock of the parent object.

      Under the existing source code control system (like IDSS and
ORBIT), if the parent object has been locked by some other users, the
user has to keep trying  until the object is available.  If the
object is heavily used by a number of users, it is possible that some
other user might check it out before he retries.  Another problem is
that some users tend to check out objects and keep them for a long
time.

      This disclosure addresses the two problems mentioned above.
There is a "ReservedCheckout" command so that users can make
reservation for a source object access.

      After the object management system receives the request, it
will first check whether the object has been che...