.

wcfs/wcfs.go

@@ -118,9 +118,9 @@
 // The filesystem server itself receives information about changed data from
 // ZODB server through regular ZODB invalidation channel (as it is ZODB client
 // itself). Then, separately for each changed file block, before actually
-// updating head/bigfile/<bigfileX> content, it notifies through head/watch to
-// clients, that had requested it (separately to each client), about the
-// changes:
+// updating head/bigfile/<bigfileX> content, it notifies through opened
+// head/watch links to clients, that had requested it (separately to each
+// client), about the changes:
 //
 //	S: <2·k> pin <bigfileX> #<blk> @<rev_max>
 //	XXX @head means unpin.
@@ -141,7 +141,7 @@
 // be potentially changed after client's <at>, and <rev_max> describes the
 // upper bound for the block revision as of <at> database view:
 //
-//	<rev_max> ≤ <at>
+//	<rev_max> ≤ <at>	; block stays unchanged in (<rev_max>, <at>] range
 //
 // The server maintains short history tail of file changes to be able to
 // support openings with <at> being slightly in the past compared to current

wcfs/wcfs_test.py

@@ -876,7 +876,7 @@ def test_wcfs():
     # XXX invalid requests -> wcfs replies error
     # XXX -> separate test?
     wl = t.openwatch()
-    assert wl.sendReq(context.background(), b'bla bla') == ""
+    assert wl.sendReq(context.background(), b'bla bla') == ""   # XXX -> == None    XXX or error?
 
     # assert wl closed
     wl.close()