I appreciate any project that makes its strengths and weaknesses very clear and documents its consistency semantics. Reading around[1], it looks like close-to-

I appreciate any project that makes its strengths and weaknesses very clear and documents its consistency semantics. Reading around[1], it looks like close-to-open consistency means that all writes must be flushed before the close() call returns, and all subsequent open() calls to the file must see the changes. IO may otherwise be buffered or cached by the FS. 1] Best source I found were these lecture slides: http://www0.cs.ucl.ac.uk/staff/B.Karp/gz03/f2011/lectures/gz03-lecture3-NFS.pdf http://www0.cs.ucl.ac.uk/staff/B.Karp/gz03/f2011/lectures/gz...