Re: New client-side locking implementation

Another open topic:

Due to the advisory nature of locks in AFS, it is still possible for
WinWord.exe on machine A to open a file with a Write Lock and then for
WordPad.exe on machine B to open the same file.   This is because
WordPad.exe does not attempt to obtain a lock.

Should the Windows client always attempt to obtain Read and Write
locks on behalf of the applications it serves whether or not the
application wants to obtain the lock?

Perhaps as part of every file open, the client should attempt to obtain
a Read lock and then release it.  At least this way, we would prevent
a file that has been locked by one machine for Writing from being opened
by another machine.

Thoughts?

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