An error occurred fetching the project authors.
- 26 Mar, 2007 1 commit
-
-
Jim Fulton authored
improved in the case that servers are restarted. Before, if transactions were committed after the restart, clients that were up to date or nearly up to date at the time of the restart and then connected had to verify their caches. Now, it is far more likely that a client that reconnects soon after a server restart won't have to verify its cache. - Fixed a serious bug that could cause clients that disconnect from and reconnect to a server to get bad invalidation data if the server serves multiple storages with active writes.
-
- 08 Mar, 2007 1 commit
-
-
Christian Theune authored
- added notice to history txt that zodb 3.8 now contains blobs :)
-
- 29 Nov, 2006 1 commit
-
-
Christian Theune authored
-
- 16 Aug, 2006 1 commit
-
-
Jim Fulton authored
problem reported on zodb-dev: http://mail.zope.org/pipermail/zodb-dev/2006-August/010343.html Added a new invalidateCache protocol for DBs and Connections to invalidate the entire in-memory caches. This is used when ZEO clients reconnect.
-
- 18 Jul, 2006 2 commits
-
-
Jim Fulton authored
test for it.
-
Jim Fulton authored
ClientStorage could be in either "sync" mode or "async" mode. Now there is just "async" mode. There is now a dedicicated asyncore main loop dedicated to ZEO clients. This addresses a test failure on Mac OS X, http://www.zope.org/Collectors/Zope3-dev/650, that I believe was due to a bug in sync mode. Some asyncore-based code was being called from multiple threads that didn't expect to be. Converting to always-async mode revealed some bugs that weren't caught before because the tests ran in sync mode. These problems could explain some problems we've seen at times with clients taking a long time to reconnect after a disconnect. Added a partial heart beat to try to detect lost connections that aren't otherwise caught, http://mail.zope.org/pipermail/zodb-dev/2005-June/008951.html, by perioidically writing to all connections during periods of inactivity.
-
- 16 Jun, 2006 1 commit
-
-
Tres Seaver authored
o Most notably, ZEO.ClientStorage (http://www.zope.org/Collectors/Zope/2016). o Forward-ported from 3.4 branch.
-
- 31 Aug, 2005 1 commit
-
-
- 23 Apr, 2005 1 commit
-
-
Tim Peters authored
ZEO version numbers the same (an auto-merge could do very little of this correctly!).
-
- 11 Mar, 2005 1 commit
-
-
Tim Peters authored
-
- 02 Jun, 2004 1 commit
-
-
Jim Fulton authored
-
- 25 Apr, 2004 2 commits
-
-
Gintautas Miliauskas authored
'test left threads behind' warnings. Tests in testZEO sometimes do that too, but that's hard to reproduce.
-
Gintautas Miliauskas authored
to zLOG other than a few comments. This definitely broke the log analyzers pretty bad.
-
- 27 Feb, 2004 1 commit
-
-
Martijn Faassen authored
-
- 18 Feb, 2004 1 commit
-
-
Jeremy Hylton authored
The old undo was not used by Zope and shouldn't have been used by any other client. The newly named undo() is the preferred version of undo. XXX DemoStorage didn't implement transactionalUndo, so now it doesn't implementation undo() at all. We need to replace it with the demo storage from ZODB4. There are a few changes related to ZODB4 removal in this checkin.
-
- 24 Dec, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 28 Nov, 2003 1 commit
-
-
Jim Fulton authored
-
- 02 Oct, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 15 Sep, 2003 1 commit
-
-
Jeremy Hylton authored
Please make all future changes on the Zope-2_7-branch instead.
-
- 06 Aug, 2003 1 commit
-
-
Tim Peters authored
+ If a storage times out between the vote and the finish, the ZEO cache could get populated with objects that don't make it to the storage server. A new flag self._midtxn_disconnect gets reset in tpc_begin() and set in notifyDisconnected(). If tpc_finish() discovers this flag set, it raises a ClientDisconnected error before calling tpc_finish() on the server. + In tpc_finish() we re-order the calls so that the server's tpc_finish() is called (and must succeed) before we update the ZEO client cache. + The storage name is now prepended to the sort key, to ensure a unique global sort order if storages are named uniquely. + Added new tests for the above (checkTimeoutAfterVote, checkTimeoutProvokingConflicts, checkSortKey).
-
- 30 May, 2003 3 commits
-
-
Jeremy Hylton authored
After the merge, I made several Python 2.1 compatibility changes for the auth code.
-
Tim Peters authored
MappingStorage (it doesn't support undo).
-
Jeremy Hylton authored
Disable test for ZEO + MappingStorage, since it doesn't support undo.
-
- 29 May, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 23 May, 2003 1 commit
-
-
Jeremy Hylton authored
Update the ZEO tests to use the new configuration language. Remove files from old configuration approach.
-
- 08 May, 2003 1 commit
-
-
Tim Peters authored
a MappingStorage (which doesn't support versions), so stop trying to test that combo.
-
- 22 Apr, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 08 Apr, 2003 2 commits
-
-
Barry Warsaw authored
-
Barry Warsaw authored
FileStorage. Fixed this and then had to no-op all the tests that MappingStorage can't possibly pass. I think there may still be problems with BDB which I'll follow up on next.
-
- 15 Jan, 2003 1 commit
-
-
Jeremy Hylton authored
ZEO.Exceptions.ClientDisconnected will always be raised when a client is disconnected. There's also a subclass of this exception in ZEO.zrpc.error so that it's possible to distinguish whether the error occurred in the RPC layer or at the storage layer.
-
- 14 Jan, 2003 2 commits
-
-
Barry Warsaw authored
-
Barry Warsaw authored
2 so they aren't normally run.
-
- 03 Jan, 2003 1 commit
-
-
Barry Warsaw authored
available or not, and also fixes to all the tests so they won't crap out or complain if not. To test whether these storages are avialable (including all package dependencies), do: import BDBStorage if BDBStorage.is_available: # okay to use Also, in BDBStorage/__init__.py do some cross-platform compatibility for the bsddb module; in Python 2.3 we can just use the built-in module, but in earlier Pythons we have to use bsddb3. Now you can just use "from BDBStorage import db" to get the proper db object.
-
- 18 Dec, 2002 1 commit
-
-
Barry Warsaw authored
bsddb3Storage becomes BDBStorage Full becomes BDBFullStorage Minimal becomes BDBMinimalStorage Removing MinimalReplicated.py, Packless.py, and base.py
-
- 13 Dec, 2002 1 commit
-
-
Barry Warsaw authored
Windows doesn't have it until Python 2.3
-
- 12 Dec, 2002 1 commit
-
-
Barry Warsaw authored
rename UnixTests to FileStorageTests, and add a simple BDBTests class to use Berkeley Full storage. Rewrite to use the new forker module api. WindowsTests: Removed.
-
- 10 Dec, 2002 1 commit
-
-
Barry Warsaw authored
module function cleanup() which was added to FileStorage and BerkeleyBase. UnixTests.getStorage(): Return a ZConfig string instead of a tuple of a class name and an argument list. BDBTests: Simple extension to UnixTests to test using Berkeley storages with ZEO. WindowsTest: Derive from UnixTests and remove getStorageInfo() and delStorage(). Add BDBTests if we can import Full.
-
- 05 Oct, 2002 1 commit
-
-
Guido van Rossum authored
-
- 03 Oct, 2002 2 commits
-
-
Guido van Rossum authored
-
Guido van Rossum authored
Got rid of PackWaitWrapper (since pack now waits by default). Moved the connection test scaffolding to testConnection.py (new); moved the openClientStorage() implementation into ConnectionTests.py since it is not platform dependent.
-