[AFS3-std] File Server/Cache Manager Extended Status Information

[Matt Benjamin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I had thought more of this would appear self-evident, but, stand corrected.

Also, regarding Jeff's initially comments (clarified for me by Jeff in
IRC), the attempt I made to address access change events in the proposal
(related to this) is indeed not coherent, and is based on a
misunderstanding of part of Jeff's intent, as he states.  I would ask
readers to focus critique on the file change notification mechanism, for
now.

I will submit a revision, with prior review (presuming that collegial
reviewers can be found), addressing in more detail the reasoning behind
suggested the suggested mechanisms, implications for the file server, as
well as the request to support the listed additional notifications
(assuming they prove uncontroversial in this forum).

Thanks for the feedback,

Matt

Jeffrey Altman wrote:
| Sure but this proposal does not describe this as future proofing or how
| the existing
| file server might be modified to perform the coalescing in a safe manner.
|
| And if there is going to be coalescing then there needs to be support
| for coalescing not
| just the DataStore operations but also all of the other operations that
| can result in
| callbacks being sent on the object.




- --

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

iD8DBQFH+V1ZJiSUUSaRdSURCM2LAJ45MxkLvwrkvPU9gQ9rzvthprv8XQCdGRi+
KbocbqrXRCQvC1WzVOMVCDg=
=jPxb
-----END PGP SIGNATURE-----