.

bigfile/_file_zodb.pyx

@@ -120,7 +120,10 @@ cdef public class _ZBigFile(BigFile) [object _ZBigFile, type _ZBigFile_Type]:
 
 
 # pywconnOf establishes and returns (py) wcfs.Conn associated with zconn.
-# XXX wconn is maintained and kept in sync with zconn.
+#
+# returned wcfs.Conn will be maintained to keep in sync with zconn.
+#
+# XXX closed on zconn dealloc ?
 # XXX simultaneous call?
 # XXX move -> .py ?
 cdef wcfs.PyConn pywconnOf(zconn):

bigfile/file_zodb.py

@@ -608,9 +608,6 @@ class ZBigFile(LivePersistent):
     # - True    -> use wcfs
     # - False   -> don't use wcfs
     # - not set -> behave according to global default
-    #
-    # XXX several fileh could be opened for one ZBigFile. Is it useful at all?
-    #     normally in one zconn there is only one zfileh opened for zfile.
     def fileh_open(self, _use_wcfs=None):
         if _use_wcfs is None:
             _use_wcfs = self._default_use_wcfs()
@@ -629,10 +626,8 @@ class ZBigFile(LivePersistent):
 
 
 
-# BigFileH wrapper that also acts as DataManager proxying changes back to ZODB
-# objects at two-phase-commit (TPC) level.
-# XXX and ZODB -> virtmem invalidation.
-# XXX split into _ZBigFileH + _ZSync ?
+# BigFileH wrapper that also acts as DataManager proxying changes ZODB <- virtmem
+# at two-phase-commit (TPC), and ZODB -> virtmem on objects invalidation.
 #
 # NOTE several fileh can be opened for ZBigFile - and this does not
 #      conflict with the way ZODB organises its work - just for fileh