Why msgpack is not enabled by default? about zeo HOT 3 CLOSED

The description you quoted tells why:

can support Python 2 or Python 3 clients (but not both)

Why should the server restrict the Python version on the client?

from zeo.

"An advantage of using msgpack for ZEO communication is that it's a tiny bit faster and a ZEO server can support Python 2 or Python 3 clients (but not both)."

That is poorly worded. Sadly, I don't recall exactly wtf I was trying to say. :)

Currently, a ZEO server and client must be running the same major version of Python, because Pickle, used in ZEO network communication, is Python-major-version specific. So today, by default, the client and server must run the same major Python version.

Because msgpack doesn't use pickle, it doesn't have this problem.

Of course, differences in pickling also make it hard for Python 2 and Python 3 clients to cooexist, so this is somewhat moot, but perhaps not entirely moot. I can imagine well-behaved Python 2 and Python 3 clients coexisting, but I haven't tried this.

msgpqck was added mainly to enable the Rust server, https://github.com/jimfulton/byteserver, but development of the Rust server hasn't advanced. (I'd really like to get back to it at some point.)

I'd be in favor of making msgpack the default at some point if I knew there was positive experience using it in production.

from zeo.

I'd be in favor of making msgpack the default at some point if I knew there was positive experience using it in production.

My company is looking for ZEO performance those times, we may give it a try!

from zeo.