- 01 Apr, 2005 27 commits
-
-
Fred Drake authored
-
Fred Drake authored
(backported from trunk revisions 29818 and 29819)
-
Fred Drake authored
-
Tim Peters authored
-
Tim Peters authored
Noet that the URL doesn't exist yet.
-
Tim Peters authored
The ZODB trunk is for 3.5 now.
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
This is news about ZEO protocol changes. The promised update of README.txt will have to be rewritten from scratch for 3.4 (the new text in 3.3's README.txt isn't quite right for the 3.4 release).
-
Tim Peters authored
This is news about ZEO protocol changes. The promised update of README.txt will have to be rewritten from scratch for 3.4 (the new text in 3.3's README.txt isn't quite right for the 3.4 release).
-
Tim Peters authored
-
Tim Peters authored
Rewrite ZEO protocol negotiation. 3.3 should have bumped the ZEO protocol number (new methods were added for MVCC support), but didn't. Untangling this is a mess.
-
Tim Peters authored
Rewrite ZEO protocol negotiation. 3.3 should have bumped the ZEO protocol number (new methods were added for MVCC support), but didn't. Untangling this is a mess.
-
Tim Peters authored
3.3 should have bumped the ZEO protocol number (new methods were added for MVCC support), but didn't. Untangling this is a mess.
-
- 31 Mar, 2005 2 commits
-
-
Tim Peters authored
the most common cases (commit() and abort()) -- it's not really obvious that shortcut spelling exist for those.
-
Tim Peters authored
the most common cases (commit() and abort()) -- it's not really obvious that shortcut spelling exist for those.
-
- 30 Mar, 2005 5 commits
-
-
Tim Peters authored
Merge checkin made from a wrong project. Believe it or not, ZopeUndo is ZEO code, not Zope code. r29726 | slinkp | 2005-03-30 02:11:22 -0500 (Wed, 30 Mar 2005) | 3 lines Changed paths: M /Zope/trunk/lib/python/ZopeUndo/Prefix.py M /Zope/trunk/lib/python/ZopeUndo/tests/testPrefix.py Merged slinkp_1726_zopeundo: avoid showing undo transactions in the wrong folder.
-
Tim Peters authored
Merge checkin made from a wrong project. Believe it or not, ZopeUndo is ZEO code, not Zope code. r29726 | slinkp | 2005-03-30 02:11:22 -0500 (Wed, 30 Mar 2005) | 3 lines Changed paths: M /Zope/trunk/lib/python/ZopeUndo/Prefix.py M /Zope/trunk/lib/python/ZopeUndo/tests/testPrefix.py Merged slinkp_1726_zopeundo: avoid showing undo transactions in the wrong folder.
-
Tim Peters authored
Believe it or not, ZopeUndo is ZEO code, not Zope code. r29726 | slinkp | 2005-03-30 02:11:22 -0500 (Wed, 30 Mar 2005) | 3 lines Changed paths: M /Zope/trunk/lib/python/ZopeUndo/Prefix.py M /Zope/trunk/lib/python/ZopeUndo/tests/testPrefix.py Merged slinkp_1726_zopeundo: avoid showing undo transactions in the wrong folder.
-
Jim Fulton authored
-
Jim Fulton authored
-
- 28 Mar, 2005 6 commits
-
-
Tim Peters authored
checkTimeoutProvokingConflicts: try to fix rare failures. This always slept for 3 seconds, waiting for the storage to disconnect. This loses on two counts: 1. Since the timeout is set to 1 second, it typically sleeps longer than necessary. 2. Since there's no predicting thread and process scheduling, 3 seconds isn't always long enough, and rare failures have been reported against this test. Instead we do a polling loop now. This typically succeeds in a little more than a second, speeding the normal case. The loop will continue trying for up to a minute if not.
-
Tim Peters authored
This always slept for 3 seconds, waiting for the storage to disconnect. This loses on two counts: 1. Since the timeout is set to 1 second, it typically sleeps longer than necessary. 2. Since there's no predicting thread and process scheduling, 3 seconds isn't always long enough, and rare failures have been reported against this test. Instead we do a polling loop now. This typically succeeds in a little more than a second, speeding the normal case. The loop will continue trying for up to a minute if not.
-
Tim Peters authored
This always slept for 3 seconds, waiting for the storage to disconnect. This loses on two counts: 1. Since the timeout is set to 1 second, it typically sleeps longer than necessary. 2. Since there's no predicting thread and process scheduling, 3 seconds isn't always long enough, and rare failures have been reported against this test. Instead we do a polling loop now. This typically succeeds in a little more than a second, speeding the normal case. The loop will continue trying for up to a minute if not.
-
Tim Peters authored
Change default port # from 9999 to 8100, to match zope.conf (well, on Zope trunk anyway -- the ZEO client example appears to have gone missing from zope.conf on Zope3 trunk).
-
Tim Peters authored
Change default port # from 9999 to 8100, to match zope.conf (well, on Zope trunk anyway -- the ZEO client example appears to have gone missing from zope.conf on Zope3 trunk).
-
Tim Peters authored
-