- 08 Jul, 2016 2 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
Python 2 support
-
- 07 Jul, 2016 24 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
After reading run_until_complete doc :)
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
Conflicts: setup.py src/ZEO/asyncio/base.py
-
Jim Fulton authored
Uvloop
-
Jim Fulton authored
Conflicts: setup.py
-
Jim Fulton authored
Client side conflict resolution
-
Jim Fulton authored
TCP_NODELAY
-
Jim Fulton authored
Conflicts: setup.py src/ZEO/tests/protocols.test
-
Jim Fulton authored
See: https://github.com/zopefoundation/ZODB/issues/84
-
Jim Fulton authored
-
Jim Fulton authored
I'm losing my love of stubs. :(
-
Jim Fulton authored
-
Jim Fulton authored
Conflicts: src/ZEO/ClientStorage.py src/ZEO/StorageServer.py
-
Jim Fulton authored
Add SSL support + It's sad no reviewer, but I suppose it can be reviewed even after a merge.
-
Jim Fulton authored
I'd missed that you could get a transport's socket using get_extra_info.
-
Jim Fulton authored
-
- 06 Jul, 2016 8 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
Conflicts: src/ZEO/ClientStorage.py
-
Jim Fulton authored
Implement iMultiCommitStorage
-
Jim Fulton authored
This is a nasty work around for: https://bugs.python.org/issue27456 It can't always be applied. For example, it can't be applied to Linux SSL sockets using the asyncio-provided loop.
-
Jim Fulton authored
-
- 05 Jul, 2016 1 commit
-
-
Jim Fulton authored
Conflicts: src/ZEO/ClientStorage.py
-
- 03 Jul, 2016 2 commits
-
-
Jim Fulton authored
And holy crap, uncommented some tests that I'd commented early while working on asyncio and forgot to uncomment before checking in.
-
Jim Fulton authored
-
- 02 Jul, 2016 2 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
As it depends on getting serials from stpre or vote
-
- 01 Jul, 2016 1 commit
-
-
Jim Fulton authored
ZEO's vote error handling was extremely and weirdly complicated. There's a hysterical explanation: Originally, the ZEO protocol was synchronous and mirrored the storage API. That was too slow, so store was made asynchronous. But then there was no way to return new serials, so we added a serialnos client API that the server called during TPC. This was used both to serials and errors. Later, tpc_vote was added, which is a synchronous method. That would have been an execllent opportunity to fix this, but noooooooooo. I'd like the server vote logic to get simpler, and we also want to get rid of serialnos, as it makes it hard to commit multiple transactions at once on the client. We can't get rid of serialnos now, because the client needs to work with old servers. Of course, nothing is easy. There was a special edge case where if the client saw an unhandled conflict error, it would invalidate it's cache for that object, allowing it to eventually recover when caches had missed invalidations. This required a change to ClientStorage, which meant that the server wouldn't work with older ZEO versions, which meant that the server could only support protocol Z5, which in tern affected protocol-negotiation tests....
-