Zeo

Latest version: v6.0.0

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

Scan your dependencies

Page 4 of 5

5.0.0a1

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

- 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

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.

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

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

- 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

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

- Add support for PyPy.

4.1.0

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

- 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

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

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

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.