[Zope3-checkins] CVS: Zope3/src/zope/fssync - README.txt:1.10
Guido van Rossum
guido@python.org
Tue, 27 May 2003 16:58:55 -0400
Update of /cvs-repository/Zope3/src/zope/fssync
In directory cvs.zope.org:/tmp/cvs-serv12311
Modified Files:
README.txt
Log Message:
Bunch of TODO items got done.
=== Zope3/src/zope/fssync/README.txt 1.9 => 1.10 ===
--- Zope3/src/zope/fssync/README.txt:1.9 Fri May 16 08:52:28 2003
+++ Zope3/src/zope/fssync/README.txt Tue May 27 16:58:55 2003
@@ -61,17 +61,6 @@
TO DO
-----
-* Rewrite fromFS to integrate uptodate checking; because the db is
- transactional it's ok to have made some changes and later raise an
- exception. Then it could also update the disk copy in-place to
- reflect changes, ready to be zipped and sent back.
-
-* Don't rely on external zip/unzip tools. Maybe switch to tar as the
- archival format, because it is easier to stream and compress at the
- same time. The file can be probably streamed right to the socket,
- without going to a temp file first, assuming the receiver can handle
- not having a Content-length header.
-
* more unit tests for fsmerge, to check that entries are handled
correctly in all cases (including addition/deletion/change of
type).
@@ -88,8 +77,6 @@
* something akin to cvs -n update, which shows what update would do
without actually doing it
-
-* commit shouldn't commit new versions of unchanged objects to ZODB
* refine the adapter protocol or implementation to leverage the
file-system representation protocol