Re: New client-side locking implementation

After several days of tweaking the byte-range locking code is certainly
stable enough for the next unstable release.   A large number of edge
cases were uncovered during testing.  The additional commits have been
applied to the same DELTA label so that it would be easy for anyone
that wants to review these changes to do so.

Eric, I believe the locking code is ready for you to use it for the IFS
as well.

Thanks to Asanka for the hard work.

Jeffrey Altman

P.S. - the promote/demote locks race condition is still an outstanding
issue.

Jeffrey Altman wrote:

> Asanka's first cut at byte range locking for the OpenAFS Windows client
> has been committed to the CVS HEAD.
> 
> http://www.openafs.org/cgi-bin/wdelta/MAIN/windows-byte-range-locks-20050816
> 
> Installers built off the head containing this code can be found at
> 
>    /afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/Head/
>    \\afs\athena.mit.edu\user\j\a\jaltman\Public\OpenAFS\Head\
>    http://web.mit.edu/jaltman/Public/OpenAFS/Head/

begin:vcard
fn:Jeffrey Altman
n:Altman;Jeffrey
org:Secure Endpoints Inc.
adr:;;255 W 94TH ST PHB;NEW YORK;NY;10025;United States
email;internet:[email protected]
title:President
tel;work:+1 212 769-9018
x-mozilla-html:TRUE
url:http://www.secure-endpoints.com
version:2.1
end:vcard