ZEO
ZEO copied to clipboard
zopefoundation
ZODB Client-Server framework
This PR tries to make the ZEO client interface implementation easier to understand; likely, the result is slightly less efficient than the current implementation. The PR switches to standard `async/await`...
to ensure that we do not store the same information twice into the cache; this may or may not be important -------- kirr: for discussion Extracted from https://github.com/zopefoundation/ZEO/pull/195
They should respond with `last_tid`.
`ClientStorage` supports several server addresses. Those addresses specify servers which essentially serve the same data, maybe a replicated storage. When `ClientStorage` connects, it tries to open protocol connections to all...
The ZEO server associates a commit lock with each of its storages, managed by a `LockManager`. The lock manager uses a `dict` to remember which connections are waiting for the...
Else those non-current entries can be used to serve a loadBefore request with data, while, after pack that loadBefore request must return "data deleted" if requested object has current revision...
testZODB from ZODB is another set of generic tests that can be reused to check storage implementations. NEO runs them. Note sure if ZODBTests is pertinent for any storage behind...
I would love to be able to use a configuration file like this: ``` address localhost:8132 address 10.xx.yy.zz:8132 ``` My company would use it to connect from our private network...
I see there is a `client-conflict-resolution` option, off by default. I could not find documentation about the advantages and drawbacks of using this option. I am guessing that: - The...
See https://stackoverflow.com/questions/58684677 I can connect to Zeo server using ssl and pure Python3, but ZEO.client() always fails. I get a TimeoutError, but I think the underlying ZEO mechanisms are hiding...
