[Zodb-checkins] CVS: ZODB3 - NEWS.txt:1.47

Jeremy Hylton jeremy at zope.com
Mon Jan 5 16:51:43 EST 2004


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

Modified Files:
	NEWS.txt 
Log Message:
Add note about changes to pickle cache (even though it happened in
3.3a1 it wasn't mentioned there).

Add Misc. and ZEO sections, add note about _map problem.


=== ZODB3/NEWS.txt 1.46 => 1.47 ===
--- ZODB3/NEWS.txt:1.46	Mon Jan  5 16:36:38 2004
+++ ZODB3/NEWS.txt	Mon Jan  5 16:51:43 2004
@@ -24,6 +24,11 @@
 - persistent.mapping.PersistentMapping
 - persistent.TimeStamp
 
+The in-memory, per-connection object cache (pickle cache) was changed
+to participate in garbage collection.  This should reduce the number
+of memory leaks, although we are still tracking a few problems.  [XXX
+might say more here]
+
 Multi-version concurrency control
 ---------------------------------
 
@@ -40,7 +45,7 @@
 conflicts.  It is possible to disable the MVCC feature using the mvcc
 keyword argument to the DB open() method, ex.: db.open(mvcc=False).
 
-Miscellaneous
+ZEO
 -------------
 
 Changed the ZEO server and control process to work with a single
@@ -56,19 +61,34 @@
 if logging was currently disabled.  Fixed to call repr() on individual
 elements until the limit is reached.
 
-ReadConflictError objects now have an ignore() method.  Normally, a
-transaction that causes a read conflict can't be committed.  If the
-exception is caught and its ignore() method called, the transaction
-can be committed.  Application code may need this in advanced
-applications.
-
 Fixed a bug in zrpc (when using authentication) where the MAC header
 wasn't being read for large messages, generating errors while unpickling
 commands sent over the wire. Also fixed the zeopasswd.py script, added
 testcases and provided a more complete commandline interface.
 
+Fixed a misuse of the _map variable in zrpc Connectio objects, which
+are also asyncore.dispatcher objects.  This allows ZEO to work with
+CVS Python (2.4). _map is used to indicate whether the dispatcher
+users the default socket_map or a custom socket_map.  A recent change
+to asyncore caused it to use _map in its add_channel() and
+del_channel() methods, which presumes to be a bug fix (may get ported
+to 2.3).  That causes our dubious use of _map to be a problem, because
+we also put the Connections in the global socket_map.  The new
+asyncore won't remove it from the global socket map, because it has a
+custom _map.
+
 The prefix used for log messages from runzeo.py was changed from
 RUNSVR to RUNZEO.
+
+Miscellaneous
+-------------
+
+ReadConflictError objects now have an ignore() method.  Normally, a
+transaction that causes a read conflict can't be committed.  If the
+exception is caught and its ignore() method called, the transaction
+can be committed.  Application code may need this in advanced
+applications.
+
 
 What's new in ZODB3 3.3 alpha 1
 ===============================




More information about the Zodb-checkins mailing list