Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site 3comvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!oliveb!3comvax!mikes
From: mikes@3comvax.UUCP (Mike Shannon)
Newsgroups: net.database,net.unix
Subject: Re: Unify Database Problems
Message-ID: <245@3comvax.UUCP>
Date: Tue, 31-Dec-85 19:52:12 EDT
Article-I.D.: 3comvax.245
Posted: Tue Dec 31 19:52:12 1985
Date-Received: Sun, 13-Oct-85 04:02:07 EDT
References: <340@luke.UUCP>
Organization: 3Com Corp; Mountain View, CA
Lines: 12
Xref: watmath net.database:100 net.unix:5866

In article <340@luke.UUCP> Bob Speray writes
> record locking?  WHO has this problem solved on Unix?  Every variant
> solution around has its limitations.  Unify uses John Bass locking
> in our environment( Plexus P60, sys3) - an absolutely exclusive lock that
> locks out reads as well as writes.   It works fine, AS DEFINED, but
> has severe limitations on concurrent reads.  It's ok for concurrent writes.

	What's the nitty gritty on 'John Bass' locking?  How about some
history, tradeoffs, etc?
	thanks,
-- 
			Michael Shannon {ihnp4,hplabs}!oliveb!3comvax!mikes