[Zodb-checkins] CVS: ZODB3 - TODO:1.1.8.5

[Jeremy Hylton]

Update of /cvs-repository/ZODB3
In directory cvs.zope.org:/tmp/cvs-serv6357

Modified Files:
      Tag: ZODB3-mvcc-2-branch
	TODO 
Log Message:
Add notes about a bunch of tasks in progress.
Add new task for 3.2/3.3 compatibility.


=== ZODB3/TODO 1.1.8.4 => 1.1.8.5 ===
--- ZODB3/TODO:1.1.8.4	Wed Nov 12 15:27:07 2003
+++ ZODB3/TODO	Thu Nov 13 16:52:05 2003
@@ -1,8 +1,43 @@
 TODO list for the MVCC branch.
 
 - Extend ZEO protocol to handle non-current data
+
+  Added loadEx() and loadNonCurrent().  Changed the load()
+  implementation on the client to use loadEx().  The primary
+  implication is that the client doesn't ask about version data
+  unless the application does.
+
+  Extend abortVersion(), commitVersion(), transactionalUndo() to
+  return an oid and a tid.
+
+  Don't have all the tests working, so I'm not sure that this is done.
+  I think that it is.
+
 - Design a mechanism for validating new ZEO cache
+
+  We want to encourage large caches, but need to make sure they aren't
+  too costly to verify.  The fast ZEO invalidation mode should be
+  useful in most cases.  If we have to fallback to "full"
+  verification, what should we do?  We might have a strategy where
+  we throw out some old things rather than asking the server whether
+  they are current.
+
 - Design and implement ZEO cache that supports non-current data
+
+  The cache API is done and the API is implemented on top of a
+  simple storage model that stores objects based on an oid, tid key.
+
+  We need to design the file-based storage mechanism.  (Use mmap?)
+
 - Implement correct loadNonCurrent for each supported storage
+
+  There is a bogus version in BaseStorage; it gets some edge cases
+  wrong.
+
+  FileStorage is done.
+
+  There are a bunch of unit tests, although they don't cover pack yet.
+
 - Document the storage API in full detail
 - Fix bug in getInvalidations() of StorageServer
+- Provide some kind of protocol compatibility between ZODB 3.2 and 3.3