Zeo

Latest version: v6.0.0

Safety actively analyzes 629765 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 5

5.0.3

Not secure
------------------

- Temporarily require non-quite-current versions of ZODB and
transaction until we can sort out some recent breakage.

5.0.2

Not secure
------------------

- 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

Not secure
------------------

Packaging-related doc fix

5.0.0

Not secure
------------------

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

Not secure
--------------------

- 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

Not secure
--------------------

- 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.

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.