============================================================
ZEO - Single-server client-server database server for ZODB
============================================================
ZEO is a client-server storage for `ZODB <http://www.zodb.org>`_ for
sharing a single storage among many clients. When you use ZEO, a
lower-level storage, typically a file storage, is opened in the ZEO
server process. Client programs connect to this process using a ZEO
ClientStorage. ZEO provides a consistent view of the database to all
clients. The ZEO client and server communicate using a custom
protocol layered on top of TCP.
Some alternatives to ZEO:
- `NEO <http://www.neoppod.org/>`_ is a distributed-server
client-server storage.
- `RelStorage <http://relstorage.readthedocs.io/en/latest/>`_
leverages the RDBMS servers to provide a client-server storage.
The documentation is available on `readthedocs <http://zeo.readthedocs.io/en/latest/>`_.
Changelog
=========
6.0.0 (2023-11-23)
------------------
- Drop support for Python 2.7, 3.5, 3.6.
- Add support for Python 3.12.
- Switch to using `async/await` directly instead of `@coroutine/yield`
- Drop experimental support for credentials object: the corresponding
``ClientStorage.__init__`` parameter ``credentials`` is retained but ignored.
From now on ZEO supports authentication only via SSL certificates.
Note that ZEO 5 never supported authenticating via ``username`` and
``password`` - support for such basic auth was dropped in 2016 before ZEO 5.0
was released.
- Fix problems with Python 3.12.0b4
(`issue 231 <https://github.com/zopefoundation/ZEO/issues/231>_`).
- Ensure test compatibility with both ``ZODB<6`` and ``ZODB>=6``
by looking for ZODB inherited tests with prefixes
``check`` (used by ``ZODB<6``)
and ``test`` (used by ``ZODB>=6``)
(`issue 233 <https://github.com/zopefoundation/ZEO/issues/233>_`).
5.4.0 (2023-01-18)
------------------
- Reimplement and streamline the ``asyncio`` part of the ``ClientStorage``
implementation:
- switch from futures with explicit callbacks to `async/await`-like style
- use standard ``asyncio`` features to implement timeouts
- redesign the API of the class implementing the ZEO client protocol
- significantly improve source documentation and tests
- fix several concurrency bugs
- add optional ``cython`` based optimization;
it speeds up reads but slows down writes.
To use it, install ``cython`` (and its dependencies) and
run ``cythonize -i *.pyx`` in ``src/ZEO/asyncio``.
- Remove support for interoperability with ZEO4 server. It turned out that ZEO5
client, contrary to interoperability with ZEO5 server, implements support for
interoperability with ZEO4 server incorrectly with concurrency bugs that lead
to data corruption. The fix is not trivial and we believe that in 2022 noone
actually uses ZEO5.client-ZEO4.server configuration. That's why support for
ZEO4 server was dropped rather than fixed.
See `issue 209 <https://github.com/zopefoundation/ZEO/issues/209>`_ for details.
- If the ``zeopack`` script cannot connect to a server it sets exit status 1
See `#214 <https://github.com/zopefoundation/ZEO/issues/214>`_.
- Remove ``asyncio/mtacceptor`` module. It turned out that multi-threaded ZEO5
server has concurrency issues that lead to data corruption. Multi-threaded
server mode was already deprecated and scheduled for removal, so the fix is
to finally remove it. From now on ZEO server is always single-threaded.
See `issue 209 <https://github.com/zopefoundation/ZEO/issues/209>`_ for details.
- Test ZEO only with the following storages
``FileStorage`` with server side blobs,
``FileStorage`` with shared blob directory,
``MappingStorage`` (without blobs).
Those tests cover all storage features with impact on ZEO:
without blobs, with shared blobs and with server side blobs;
load, store, two phase commit, undo.
Therefore, passing tests for those storages provide high confidence that ZEO
works for other properly implemented storages as well.
See `#198 <https://github.com/zopefoundation/ZEO/issues/198>`_.
- Lint the code with flake8
- Add support for Python 3.10, 3.11.
- Add ``ConflictError`` to the list of unlogged server exceptions
(the client/its application should determine whether it wants
them logged).
Prevent ``no current transaction: tpc_abort()`` server log entries.
The storage API allows ``tpc_abort`` to be called with an
invalid transaction (the call should be ignored in this case)
and the server's ``tpc_vote`` relies on this.
Change the server's log message label for request exceptions
from ``Bad request ...`` to ``... raised exception:``,
hinting towards a server rather than client problem.
See `issue 156 <https://github.com/zopefoundation/ZEO/issues/156>`_.
- Remove support for ``python setup.py test``. It hadn't been working
for some time. From now the only supported way to run tests is via
``zope-testrunner``.
5.3.0 (2022-03-24)
------------------
- Remove tests for the ``asyncio/mtacceptor`` module, it appears unused
and presents a maintenance burden. The module will be removed in
ZEO version 6.
- Remove GitHub Actions testing for Python 3.5, it has reached end of life.
- Add support for Python 3.8 and Python 3.9.
- Add more accurate error handling for ``asyncio.CancelledError``.
See `issue 165 <https://github.com/zopefoundation/ZEO/issues/165>`_.
- Fix bug related to blobs stored by ``ZEO``
`#150 <https://github.com/zopefoundation/ZEO/issues/150>`_.
5.2.3 (2021-08-09)
------------------
- Ensure ``ZEO`` satisfies the ``ZODB >= 5.6`` requirement that
``lastTransaction()`` changes only after invalidation processing.
Violating this requirement can lead to race conditions and
associated data corruption
`#166 <https://github.com/zopefoundation/ZEO/issues/166>`_.
- Add automated tests against the ZODB ``master`` branch
see `issue 177 <https://github.com/zopefoundation/ZEO/issues/177>`_.
- Fix data corruption due to race between load and external invalidations.
See `issue 155 <https://github.com/zopefoundation/ZEO/issues/155>`_.
- Improve log message when client cache is out of sync with server.
See `issue 142 <https://github.com/zopefoundation/ZEO/issues/142>`_.
5.2.2 (2020-08-11)
------------------
- Remove support for Python 3.4
- Provide proper CA test certificates to allow the SSL tests succeed for Py3
- Replace deprecated occurrences of ``Thread.isAlive()`` by ``Thread.is_alive()``
See `pull request 154 <https://github.com/zopefoundation/ZEO/pull/154>`_.
- Include both modified and just created objects into invalidations.
See `pull request 160 <https://github.com/zopefoundation/ZEO/pull/160>`_.
5.2.1 (2019-02-09)
------------------
- Add support for Python 3.7.
- Switch from ``msgpack-python`` to ``msgpack``. Currently a version < 0.6
is required.
- Stop calling the deprecated ``checkSecure`` method when creating a
``ClientStorage``. With ZODB 5.2.2 and above, this issued a warning.
With older versions, this *could* issue a log message, but this was
considered `a misfeature
<https://github.com/zopefoundation/ZODB/issues/155>`_. See `issue
134 <https://github.com/zopefoundation/ZEO/issues/134>`_.
5.2.0 (2018-03-28)
------------------
- Fixed: The quickstart/ad-hoc/play ZEO server relied on test
dependencies. See `issue 105
<https://github.com/zopefoundation/ZEO/issues/105>`_.
- Disallow passing strings as addresses to ClientStorage under Windows
because string addresses are used for unix-domain sockets, which
aren't supported on Windows. See `issue 107
<https://github.com/zopefoundation/ZEO/issues/107>`_.
- Renamed all ``async`` attributes to ``async_`` for compatibility
with Python 3.7. See `issue 104
<https://github.com/zopefoundation/ZEO/issues/104>`_.
- Fixed to work with some changes made in ZODB 5.4.0.
Client-side updates are included for ZODB 5.4.0 or databases that
already had ``zodbpickle.binary`` OIDs. See `issue 113
<https://github.com/zopefoundation/ZEO/issues/113>`_.
- ZEO now uses pickle protocol 3 for both Python 2 and Python 3.
(Previously protocol 1 was used for Python 2.) This matches the
change in ZODB 5.4.0.
5.1.2 (2018-03-27)
------------------
- Fix: ZEO didn't work with a change in ZODB 5.4.0.
(Allow ``zodbpickle.binary`` to be used in RPC requests, which is
necessary for compatibility with ZODB 5.4.0 on Python 2. See `issue
107 <https://github.com/zopefoundation/ZEO/issues/107>`_.)
5.1.1 (2017-12-18)
------------------
- All classes are new-style classes on Python 2 (they were already
new-style on Python 3). This improves performance on PyPy. See
`issue 86 <https://github.com/zopefoundation/ZEO/pull/86>`_.
- Fixed removing UNIX socket files under Python 2 with ZConfig 3.2.0.
See `issue 90 <https://github.com/zopefoundation/ZEO/issues/90>`_.
5.1.0 (2017-04-03)
------------------
- Added support for serializing ZEO messages using `msgpack
<http://msgpack.org/index.html>`_ rather than pickle. This helps
pave the way to supporting `byteserver
<https://github.com/jimfulton/byteserver>`_, but it also allows ZEO
servers to support Python 2 or 3 clients (but not both at the same
time) and may provide a small performance improvement.
- Possibly fixed the deprecated and untested zeoctl script.
- Removed zeopasswd, which no longer makes sense given that ZEO
authentication was removed, in favor of SSL.
5.0.4 (2016-11-18)
------------------
- Fixed: ZEO needed changes to work with recent transaction changes.
ZEO now works with the latest versions of ZODB and transaction
5.0.3 (2016-11-18)
------------------
- Temporarily require non-quite-current versions of ZODB and
transaction until we can sort out some recent breakage.
5.0.2 (2016-11-02)
------------------
- Provide much better performance on Python 2.
- Provide better error messages when pip tries to install ZEO on an
unsupported Python version. See `issue 75
<https://github.com/zopefoundation/ZEO/issues/75>`_.
5.0.1 (2016-09-06)
------------------
Packaging-related doc fix
5.0.0 (2016-09-06)
------------------
This is a major ZEO revision, which replaces the ZEO network protocol
implementation.
New features:
- SSL support
- Optional client-side conflict resolution.
- Lots of mostly internal clean ups.
- ``ClientStorage``server-sync`` configuration option and
``server_sync`` constructor argument to force a server round trip at
the beginning of transactions to wait for any outstanding
invalidations at the start of the transaction to be delivered.
- Client disconnect errors are now transient errors. When
applications retry jobs that raise transient errors, jobs (e.g. web
requests) with disconnect errors will be retried. Together with
blocking synchronous ZEO server calls for a limited time while
disconnected, this change should allow brief disconnections due to
server restart to avoid generating client-visible errors (e.g. 500
web responses).
- ClientStorage prefetch method to prefetch oids.
When oids are prefetched, requests are made at once, but the caller
doesn't block waiting for the results. Rather, then the caller
later tries to fetch data for one of the object ids, it's either
delivered right away from the ZEO cache, if the prefetch for the
object id has completed, or the caller blocks until the inflight
prefetch completes. (No new request is made.)
Dropped features:
- The ZEO authentication protocol.
This will be replaced by new authentication mechanims leveraging SSL.
- The ZEO monitor server.
- Full cache verification.
- Client suppprt for servers older than ZODB 3.9
- Server support for clients older than ZEO 4.2.0
5.0.0b0 (2016-08-18)
--------------------
- Added a ``ClientStorage`` ``server-sync`` configuration option and
``server_sync`` constructor argument to force a server round trip at
the beginning of transactions to wait for any outstanding
invalidations at the start of the transaction to be delivered.
- When creating an ad hoc server, a log file isn't created by
default. You must pass a ``log`` option specifying a log file name.
- The ZEO server register method now returns the storage last
transaction, allowing the client to avoid an extra round trip during
cache verification.
- Client disconnect errors are now transient errors. When
applications retry jobs that raise transient errors, jobs (e.g. web
requests) with disconnect errors will be retried. Together with
blocking synchronous ZEO server calls for a limited time while
disconnected, this change should allow brief disconnections due to
server restart to avoid generating client-visible errors (e.g. 500
web responses).
- Fixed bugs in using the ZEO 5 client with ZEO 4 servers.
5.0.0a2 (2016-07-30)
--------------------
- Added the ability to pass credentials when creating client storages.
This is experimental in that passing credentials will cause
connections to an ordinary ZEO server to fail, but it facilitates
experimentation with custom ZEO servers. Doing this with custom ZEO
clients would have been awkward due to the many levels of
composition involved.
In the future, we expect to support server security plugins that
consume credentials for authentication (typically over SSL).
Note that credentials are opaque to ZEO. They can be any object with
a true value. The client mearly passes them to the server, which
will someday pass them to a plugin.
5.0.0a1 (2016-07-21)
--------------------
- Added a ClientStorage prefetch method to prefetch oids.
When oids are prefetched, requests are made at once, but the caller
doesn't block waiting for the results. Rather, then the caller
later tries to fetch data for one of the object ids, it's either
delivered right away from the ZEO cache, if the prefetch for the
object id has completed, or the caller blocks until the inflight
prefetch completes. (No new request is made.)
- Fixed: SSL clients of servers with signed certs didn't load default
certs and were unable to connect.
5.0.0a0 (2016-07-08)
--------------------
This is a major ZEO revision, which replaces the ZEO network protocol
implementation.
New features:
- SSL support
- Optional client-side conflict resolution.
- Lots of mostly internal clean ups.
Dropped features:
- The ZEO authentication protocol.
This will be replaced by new authentication mechanims leveraging SSL.
- The ZEO monitor server.
- Full cache verification.
- Client suppprt for servers older than ZODB 3.9
- Server support for clients older than ZEO 4.2.0
4.2.0 (2016-06-15)
------------------
- Changed loadBefore to operate more like load behaved, especially
with regard to the load lock. This allowes ZEO to work with the
upcoming ZODB 5, which used loadbefore rather than load.
Reimplemented load using loadBefore, thus testing loadBefore
extensively via existing tests.
- Other changes to work with ZODB 5 (as well as ZODB 4)
- Fixed: the ZEO cache loadBefore method failed to utilize current data.
- Drop support for Python 2.6 and 3.2.
- Fix AttributeError: 'ZEOServer' object has no attribute 'server' when
StorageServer creation fails.
4.2.0b1 (2015-06-05)
--------------------
- Add support for PyPy.
4.1.0 (2015-01-06)
------------------
- Add support for Python 3.4.
- Added a new ``ruok`` client protocol for getting server status on
the ZEO port without creating a full-blown client connection and
without logging in the server log.
- Log errors on server side even if using multi threaded delay.
4.0.0 (2013-08-18)
------------------
- Avoid reading excess random bytes when setting up an auth_digest session.
- Optimize socket address enumeration in ZEO client (avoid non-TCP types).
- Improve Travis CI testing support.
- Assign names to all threads for better runtime debugging.
- Fix "assignment to keyword" error under Py3k in 'ZEO.scripts.zeoqueue'.
4.0.0b1 (2013-05-20)
--------------------
- Depend on ZODB >= 4.0.0b2
- Add support for Python 3.2 / 3.3.
4.0.0a1 (2012-11-19)
--------------------
First (in a long time) separate ZEO release.
Since ZODB 3.10.5:
- Storage servers now emit Serving and Closed events so subscribers
can discover addresses when dynamic port assignment (bind to port 0)
is used. This could, for example, be used to update address
information in a ZooKeeper database.
- Client storages have a method, new_addr, that can be used to change
the server address(es). This can be used, for example, to update a
dynamically determined server address from information in a
ZooKeeper database.
Raw data
{
"_id": null,
"home_page": "https://github.com/zopefoundation/ZEO",
"name": "ZEO",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.7",
"maintainer_email": "",
"keywords": "database,zodb",
"author": "Zope Foundation and Contributors",
"author_email": "zodb@googlegroups.com",
"download_url": "https://files.pythonhosted.org/packages/1a/85/ab008e84445dcd39b2d079fdc7eb5475d5597de9504e2a0cb6bb44ca9a4b/ZEO-6.0.0.tar.gz",
"platform": "any",
"description": "============================================================\nZEO - Single-server client-server database server for ZODB\n============================================================\n\nZEO is a client-server storage for `ZODB <http://www.zodb.org>`_ for\nsharing a single storage among many clients. When you use ZEO, a\nlower-level storage, typically a file storage, is opened in the ZEO\nserver process. Client programs connect to this process using a ZEO\nClientStorage. ZEO provides a consistent view of the database to all\nclients. The ZEO client and server communicate using a custom\nprotocol layered on top of TCP.\n\nSome alternatives to ZEO:\n\n- `NEO <http://www.neoppod.org/>`_ is a distributed-server\n client-server storage.\n\n- `RelStorage <http://relstorage.readthedocs.io/en/latest/>`_\n leverages the RDBMS servers to provide a client-server storage.\n\nThe documentation is available on `readthedocs <http://zeo.readthedocs.io/en/latest/>`_.\n\nChangelog\n=========\n\n6.0.0 (2023-11-23)\n------------------\n\n- Drop support for Python 2.7, 3.5, 3.6.\n\n- Add support for Python 3.12.\n\n- Switch to using `async/await` directly instead of `@coroutine/yield`\n\n- Drop experimental support for credentials object: the corresponding\n ``ClientStorage.__init__`` parameter ``credentials`` is retained but ignored.\n From now on ZEO supports authentication only via SSL certificates.\n\n Note that ZEO 5 never supported authenticating via ``username`` and\n ``password`` - support for such basic auth was dropped in 2016 before ZEO 5.0\n was released.\n\n- Fix problems with Python 3.12.0b4\n (`issue 231 <https://github.com/zopefoundation/ZEO/issues/231>_`).\n\n- Ensure test compatibility with both ``ZODB<6`` and ``ZODB>=6``\n by looking for ZODB inherited tests with prefixes\n ``check`` (used by ``ZODB<6``)\n and ``test`` (used by ``ZODB>=6``)\n (`issue 233 <https://github.com/zopefoundation/ZEO/issues/233>_`).\n\n\n5.4.0 (2023-01-18)\n------------------\n\n- Reimplement and streamline the ``asyncio`` part of the ``ClientStorage``\n implementation:\n\n - switch from futures with explicit callbacks to `async/await`-like style\n - use standard ``asyncio`` features to implement timeouts\n - redesign the API of the class implementing the ZEO client protocol\n - significantly improve source documentation and tests\n - fix several concurrency bugs\n - add optional ``cython`` based optimization;\n it speeds up reads but slows down writes.\n To use it, install ``cython`` (and its dependencies) and\n run ``cythonize -i *.pyx`` in ``src/ZEO/asyncio``.\n\n- Remove support for interoperability with ZEO4 server. It turned out that ZEO5\n client, contrary to interoperability with ZEO5 server, implements support for\n interoperability with ZEO4 server incorrectly with concurrency bugs that lead\n to data corruption. The fix is not trivial and we believe that in 2022 noone\n actually uses ZEO5.client-ZEO4.server configuration. That's why support for\n ZEO4 server was dropped rather than fixed.\n\n See `issue 209 <https://github.com/zopefoundation/ZEO/issues/209>`_ for details.\n\n- If the ``zeopack`` script cannot connect to a server it sets exit status 1\n See `#214 <https://github.com/zopefoundation/ZEO/issues/214>`_.\n\n- Remove ``asyncio/mtacceptor`` module. It turned out that multi-threaded ZEO5\n server has concurrency issues that lead to data corruption. Multi-threaded\n server mode was already deprecated and scheduled for removal, so the fix is\n to finally remove it. From now on ZEO server is always single-threaded.\n\n See `issue 209 <https://github.com/zopefoundation/ZEO/issues/209>`_ for details.\n\n- Test ZEO only with the following storages\n ``FileStorage`` with server side blobs,\n ``FileStorage`` with shared blob directory,\n ``MappingStorage`` (without blobs).\n\n Those tests cover all storage features with impact on ZEO:\n without blobs, with shared blobs and with server side blobs;\n load, store, two phase commit, undo.\n Therefore, passing tests for those storages provide high confidence that ZEO\n works for other properly implemented storages as well.\n See `#198 <https://github.com/zopefoundation/ZEO/issues/198>`_.\n\n- Lint the code with flake8\n\n- Add support for Python 3.10, 3.11.\n\n- Add ``ConflictError`` to the list of unlogged server exceptions\n (the client/its application should determine whether it wants\n them logged).\n\n Prevent ``no current transaction: tpc_abort()`` server log entries.\n The storage API allows ``tpc_abort`` to be called with an\n invalid transaction (the call should be ignored in this case)\n and the server's ``tpc_vote`` relies on this.\n\n Change the server's log message label for request exceptions\n from ``Bad request ...`` to ``... raised exception:``,\n hinting towards a server rather than client problem.\n\n See `issue 156 <https://github.com/zopefoundation/ZEO/issues/156>`_.\n\n- Remove support for ``python setup.py test``. It hadn't been working\n for some time. From now the only supported way to run tests is via\n ``zope-testrunner``.\n\n\n5.3.0 (2022-03-24)\n------------------\n\n- Remove tests for the ``asyncio/mtacceptor`` module, it appears unused\n and presents a maintenance burden. The module will be removed in\n ZEO version 6.\n\n- Remove GitHub Actions testing for Python 3.5, it has reached end of life.\n\n- Add support for Python 3.8 and Python 3.9.\n\n- Add more accurate error handling for ``asyncio.CancelledError``.\n See `issue 165 <https://github.com/zopefoundation/ZEO/issues/165>`_.\n\n- Fix bug related to blobs stored by ``ZEO``\n `#150 <https://github.com/zopefoundation/ZEO/issues/150>`_.\n\n\n5.2.3 (2021-08-09)\n------------------\n\n- Ensure ``ZEO`` satisfies the ``ZODB >= 5.6`` requirement that\n ``lastTransaction()`` changes only after invalidation processing.\n Violating this requirement can lead to race conditions and\n associated data corruption\n `#166 <https://github.com/zopefoundation/ZEO/issues/166>`_.\n\n- Add automated tests against the ZODB ``master`` branch\n see `issue 177 <https://github.com/zopefoundation/ZEO/issues/177>`_.\n\n- Fix data corruption due to race between load and external invalidations.\n See `issue 155 <https://github.com/zopefoundation/ZEO/issues/155>`_.\n\n- Improve log message when client cache is out of sync with server.\n See `issue 142 <https://github.com/zopefoundation/ZEO/issues/142>`_.\n\n5.2.2 (2020-08-11)\n------------------\n\n- Remove support for Python 3.4\n\n- Provide proper CA test certificates to allow the SSL tests succeed for Py3\n\n- Replace deprecated occurrences of ``Thread.isAlive()`` by ``Thread.is_alive()``\n See `pull request 154 <https://github.com/zopefoundation/ZEO/pull/154>`_.\n\n- Include both modified and just created objects into invalidations.\n See `pull request 160 <https://github.com/zopefoundation/ZEO/pull/160>`_.\n\n\n5.2.1 (2019-02-09)\n------------------\n\n- Add support for Python 3.7.\n\n- Switch from ``msgpack-python`` to ``msgpack``. Currently a version < 0.6\n is required.\n\n- Stop calling the deprecated ``checkSecure`` method when creating a\n ``ClientStorage``. With ZODB 5.2.2 and above, this issued a warning.\n With older versions, this *could* issue a log message, but this was\n considered `a misfeature\n <https://github.com/zopefoundation/ZODB/issues/155>`_. See `issue\n 134 <https://github.com/zopefoundation/ZEO/issues/134>`_.\n\n\n5.2.0 (2018-03-28)\n------------------\n\n- Fixed: The quickstart/ad-hoc/play ZEO server relied on test\n dependencies. See `issue 105\n <https://github.com/zopefoundation/ZEO/issues/105>`_.\n\n- Disallow passing strings as addresses to ClientStorage under Windows\n because string addresses are used for unix-domain sockets, which\n aren't supported on Windows. See `issue 107\n <https://github.com/zopefoundation/ZEO/issues/107>`_.\n\n- Renamed all ``async`` attributes to ``async_`` for compatibility\n with Python 3.7. See `issue 104\n <https://github.com/zopefoundation/ZEO/issues/104>`_.\n\n- Fixed to work with some changes made in ZODB 5.4.0.\n\n Client-side updates are included for ZODB 5.4.0 or databases that\n already had ``zodbpickle.binary`` OIDs. See `issue 113\n <https://github.com/zopefoundation/ZEO/issues/113>`_.\n\n- ZEO now uses pickle protocol 3 for both Python 2 and Python 3.\n (Previously protocol 1 was used for Python 2.) This matches the\n change in ZODB 5.4.0.\n\n5.1.2 (2018-03-27)\n------------------\n\n- Fix: ZEO didn't work with a change in ZODB 5.4.0.\n\n (Allow ``zodbpickle.binary`` to be used in RPC requests, which is\n necessary for compatibility with ZODB 5.4.0 on Python 2. See `issue\n 107 <https://github.com/zopefoundation/ZEO/issues/107>`_.)\n\n5.1.1 (2017-12-18)\n------------------\n\n- All classes are new-style classes on Python 2 (they were already\n new-style on Python 3). This improves performance on PyPy. See\n `issue 86 <https://github.com/zopefoundation/ZEO/pull/86>`_.\n\n- Fixed removing UNIX socket files under Python 2 with ZConfig 3.2.0.\n See `issue 90 <https://github.com/zopefoundation/ZEO/issues/90>`_.\n\n5.1.0 (2017-04-03)\n------------------\n\n- Added support for serializing ZEO messages using `msgpack\n <http://msgpack.org/index.html>`_ rather than pickle. This helps\n pave the way to supporting `byteserver\n <https://github.com/jimfulton/byteserver>`_, but it also allows ZEO\n servers to support Python 2 or 3 clients (but not both at the same\n time) and may provide a small performance improvement.\n\n- Possibly fixed the deprecated and untested zeoctl script.\n\n- Removed zeopasswd, which no longer makes sense given that ZEO\n authentication was removed, in favor of SSL.\n\n5.0.4 (2016-11-18)\n------------------\n\n- Fixed: ZEO needed changes to work with recent transaction changes.\n\n ZEO now works with the latest versions of ZODB and transaction\n\n5.0.3 (2016-11-18)\n------------------\n\n- Temporarily require non-quite-current versions of ZODB and\n transaction until we can sort out some recent breakage.\n\n5.0.2 (2016-11-02)\n------------------\n\n- Provide much better performance on Python 2.\n\n- Provide better error messages when pip tries to install ZEO on an\n unsupported Python version. See `issue 75\n <https://github.com/zopefoundation/ZEO/issues/75>`_.\n\n5.0.1 (2016-09-06)\n------------------\n\nPackaging-related doc fix\n\n5.0.0 (2016-09-06)\n------------------\n\nThis is a major ZEO revision, which replaces the ZEO network protocol\nimplementation.\n\nNew features:\n\n- SSL support\n\n- Optional client-side conflict resolution.\n\n- Lots of mostly internal clean ups.\n\n- ``ClientStorage``server-sync`` configuration option and\n ``server_sync`` constructor argument to force a server round trip at\n the beginning of transactions to wait for any outstanding\n invalidations at the start of the transaction to be delivered.\n\n- Client disconnect errors are now transient errors. When\n applications retry jobs that raise transient errors, jobs (e.g. web\n requests) with disconnect errors will be retried. Together with\n blocking synchronous ZEO server calls for a limited time while\n disconnected, this change should allow brief disconnections due to\n server restart to avoid generating client-visible errors (e.g. 500\n web responses).\n\n- ClientStorage prefetch method to prefetch oids.\n\n When oids are prefetched, requests are made at once, but the caller\n doesn't block waiting for the results. Rather, then the caller\n later tries to fetch data for one of the object ids, it's either\n delivered right away from the ZEO cache, if the prefetch for the\n object id has completed, or the caller blocks until the inflight\n prefetch completes. (No new request is made.)\n\nDropped features:\n\n- The ZEO authentication protocol.\n\n This will be replaced by new authentication mechanims leveraging SSL.\n\n- The ZEO monitor server.\n\n- Full cache verification.\n\n- Client suppprt for servers older than ZODB 3.9\n\n- Server support for clients older than ZEO 4.2.0\n\n5.0.0b0 (2016-08-18)\n--------------------\n\n- Added a ``ClientStorage`` ``server-sync`` configuration option and\n ``server_sync`` constructor argument to force a server round trip at\n the beginning of transactions to wait for any outstanding\n invalidations at the start of the transaction to be delivered.\n\n- When creating an ad hoc server, a log file isn't created by\n default. You must pass a ``log`` option specifying a log file name.\n\n- The ZEO server register method now returns the storage last\n transaction, allowing the client to avoid an extra round trip during\n cache verification.\n\n- Client disconnect errors are now transient errors. When\n applications retry jobs that raise transient errors, jobs (e.g. web\n requests) with disconnect errors will be retried. Together with\n blocking synchronous ZEO server calls for a limited time while\n disconnected, this change should allow brief disconnections due to\n server restart to avoid generating client-visible errors (e.g. 500\n web responses).\n\n- Fixed bugs in using the ZEO 5 client with ZEO 4 servers.\n\n5.0.0a2 (2016-07-30)\n--------------------\n\n- Added the ability to pass credentials when creating client storages.\n\n This is experimental in that passing credentials will cause\n connections to an ordinary ZEO server to fail, but it facilitates\n experimentation with custom ZEO servers. Doing this with custom ZEO\n clients would have been awkward due to the many levels of\n composition involved.\n\n In the future, we expect to support server security plugins that\n consume credentials for authentication (typically over SSL).\n\n Note that credentials are opaque to ZEO. They can be any object with\n a true value. The client mearly passes them to the server, which\n will someday pass them to a plugin.\n\n5.0.0a1 (2016-07-21)\n--------------------\n\n- Added a ClientStorage prefetch method to prefetch oids.\n\n When oids are prefetched, requests are made at once, but the caller\n doesn't block waiting for the results. Rather, then the caller\n later tries to fetch data for one of the object ids, it's either\n delivered right away from the ZEO cache, if the prefetch for the\n object id has completed, or the caller blocks until the inflight\n prefetch completes. (No new request is made.)\n\n- Fixed: SSL clients of servers with signed certs didn't load default\n certs and were unable to connect.\n\n5.0.0a0 (2016-07-08)\n--------------------\n\nThis is a major ZEO revision, which replaces the ZEO network protocol\nimplementation.\n\nNew features:\n\n- SSL support\n\n- Optional client-side conflict resolution.\n\n- Lots of mostly internal clean ups.\n\nDropped features:\n\n- The ZEO authentication protocol.\n\n This will be replaced by new authentication mechanims leveraging SSL.\n\n- The ZEO monitor server.\n\n- Full cache verification.\n\n- Client suppprt for servers older than ZODB 3.9\n\n- Server support for clients older than ZEO 4.2.0\n\n4.2.0 (2016-06-15)\n------------------\n\n- Changed loadBefore to operate more like load behaved, especially\n with regard to the load lock. This allowes ZEO to work with the\n upcoming ZODB 5, which used loadbefore rather than load.\n\n Reimplemented load using loadBefore, thus testing loadBefore\n extensively via existing tests.\n\n- Other changes to work with ZODB 5 (as well as ZODB 4)\n\n- Fixed: the ZEO cache loadBefore method failed to utilize current data.\n\n- Drop support for Python 2.6 and 3.2.\n\n- Fix AttributeError: 'ZEOServer' object has no attribute 'server' when\n StorageServer creation fails.\n\n4.2.0b1 (2015-06-05)\n--------------------\n\n- Add support for PyPy.\n\n4.1.0 (2015-01-06)\n------------------\n\n- Add support for Python 3.4.\n\n- Added a new ``ruok`` client protocol for getting server status on\n the ZEO port without creating a full-blown client connection and\n without logging in the server log.\n\n- Log errors on server side even if using multi threaded delay.\n\n4.0.0 (2013-08-18)\n------------------\n\n- Avoid reading excess random bytes when setting up an auth_digest session.\n\n- Optimize socket address enumeration in ZEO client (avoid non-TCP types).\n\n- Improve Travis CI testing support.\n\n- Assign names to all threads for better runtime debugging.\n\n- Fix \"assignment to keyword\" error under Py3k in 'ZEO.scripts.zeoqueue'.\n\n4.0.0b1 (2013-05-20)\n--------------------\n\n- Depend on ZODB >= 4.0.0b2\n\n- Add support for Python 3.2 / 3.3.\n\n4.0.0a1 (2012-11-19)\n--------------------\n\nFirst (in a long time) separate ZEO release.\n\nSince ZODB 3.10.5:\n\n- Storage servers now emit Serving and Closed events so subscribers\n can discover addresses when dynamic port assignment (bind to port 0)\n is used. This could, for example, be used to update address\n information in a ZooKeeper database.\n\n- Client storages have a method, new_addr, that can be used to change\n the server address(es). This can be used, for example, to update a\n dynamically determined server address from information in a\n ZooKeeper database.\n",
"bugtrack_url": null,
"license": "ZPL 2.1",
"summary": "ZEO - Single-server client-server database server for ZODB",
"version": "6.0.0",
"project_urls": {
"Homepage": "https://github.com/zopefoundation/ZEO"
},
"split_keywords": [
"database",
"zodb"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "ce36dfb1aa57d58f39745dd97873c10be8568e4b19ec2c5d139dc3c62ccd70e5",
"md5": "bdcd1a83fc67c36297ccd061a59cb806",
"sha256": "4fd6569e00a6f9c91fdfe7d917887666893252be7c0a6e4afc3901ef8d4b4ae5"
},
"downloads": -1,
"filename": "ZEO-6.0.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "bdcd1a83fc67c36297ccd061a59cb806",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.7",
"size": 247161,
"upload_time": "2023-11-23T07:10:44",
"upload_time_iso_8601": "2023-11-23T07:10:44.287548Z",
"url": "https://files.pythonhosted.org/packages/ce/36/dfb1aa57d58f39745dd97873c10be8568e4b19ec2c5d139dc3c62ccd70e5/ZEO-6.0.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "1a85ab008e84445dcd39b2d079fdc7eb5475d5597de9504e2a0cb6bb44ca9a4b",
"md5": "d13665162cbdc42abfaa8e61305efc67",
"sha256": "be238b5abf9ea3396935b33530f66a9afa61ccf8b6b813c2cfdcb2aa18541be7"
},
"downloads": -1,
"filename": "ZEO-6.0.0.tar.gz",
"has_sig": false,
"md5_digest": "d13665162cbdc42abfaa8e61305efc67",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.7",
"size": 243635,
"upload_time": "2023-11-23T07:10:47",
"upload_time_iso_8601": "2023-11-23T07:10:47.132539Z",
"url": "https://files.pythonhosted.org/packages/1a/85/ab008e84445dcd39b2d079fdc7eb5475d5597de9504e2a0cb6bb44ca9a4b/ZEO-6.0.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-11-23 07:10:47",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "zopefoundation",
"github_project": "ZEO",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"tox": true,
"lcname": "zeo"
}
JSON
