-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Sorry, correction:
The fileserver must synchronously deliver any callbacks pending on Fid to Client when client requests the read lock. Matt Chaskiel M Grundman wrote: >> That's supposed to be handled by implementing a write barrier on lock >> release. Tom had indicated this in conversation, too. > That already happens. releasing a write lock does write back the contents > before releasing the lock. how is client 1 supposed to implement the > corresponding read barrier if callback delivery is not synchronous? Do you > want it to do an extra fetchstatus after the lock succeeds? - -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 http://linuxbox.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJB2wZJiSUUSaRdSURCCRKAJ4i6g/dkc4d10JkWXthAasq57VoGACeJgqj fyzJDneb9GNDTyB9P3RtZ9g= =SZ45 -----END PGP SIGNATURE----- _______________________________________________ AFS3-standardization mailing list [email protected] http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization
