[Zope3-checkins] CVS: Zope3/src/zope/fssync - README.txt:1.22

[Guido van Rossum]

Update of /cvs-repository/Zope3/src/zope/fssync
In directory cvs.zope.org:/tmp/cvs-serv20741/zope/fssync

Modified Files:
	README.txt 
Log Message:
Refactored the Committer class, separating it out (again!) into a
Checker class and a Committer class.  The Committer class no longer
modifies the filesystem; that's toFS()'s responsibility (also due for
a rewrite).  The unit tests for Committer are much more sensible now.


=== Zope3/src/zope/fssync/README.txt 1.21 => 1.22 ===
--- Zope3/src/zope/fssync/README.txt:1.21	Mon Jun  2 15:50:31 2003
+++ Zope3/src/zope/fssync/README.txt	Tue Jun  3 13:08:53 2003
@@ -59,21 +59,6 @@
   tries to send the request to a view of the corresponding object,
   which doesn't exist yet.
 
-* When dealing with additions or removals, sometimes multiple updates
-  are required to get the Extra stuff to be updated.
-
-* Removing a directory tree doesn't work intuitively; if you "rm -r" a
-  subtree and then "sync remove" it, a following "sync commit" causes
-  a server-side exception.  It should just work.  (As a work-around,
-  you can remove individual files and commit those removals first,
-  then remove the directory last.)
-
-* When committing something creates additional stuff (for example,
-  committing an added site folder creates a RegistrationManager inside
-  the site folder), the commit operation doesn't send the created
-  stuff back necessarily.  (As a work-around, a subsequent update gets
-  them.)
-
 * Removing an object with annotations doesn't always remove the
   @@Zope/Annotations/<name>/ directory.  Probably the same for Extra.
 
@@ -86,11 +71,7 @@
 
 - On the server side:
 
-  * Should be able to add various standard object types based on
-    filename extension.  (This now works for extensions .pt and .dtml,
-    and for .py extensions in the ++etc++site tree; for other
-    extensions, either an image or a plain file is created based on
-    the extension and the contents.  Is this good enough?)
+  * Nothing ATM.
 
 - In the sync application:
 
@@ -108,11 +89,13 @@
 
 - Code maintenance:
 
-  * Unit tests for the fssync core functionality.
+  * Rewrite toFS() to use the Metadata class, and add unit tests.
+
+  * Unit tests for the fssync utility.
 
-  * More refactoring and cleanup of the fssync core functionality.
+  * More refactoring and cleanup of the fssync utility.
 
-  * Use camelCase for method names.
+  * Use camelCase for public method names.
 
 
 TO DO LATER