On Fri, Sep 26, 2014 at 10:37 AM, Goswin von Brederlow <goswin-...@web.de> wrote:
> If the two get merged then why not merge the zsock class with the > libzqm socket structure. Use it as is for the zsock interface and cast > it to void * for the sake of the old API. A true merge and not just > layering the czmq API over the old one. For sure. I'd keep the polymophism between e.g. zactor and zsock. However one goal would be to kill and bury the old void * socket type. In CZMQ we've already killed contexts, and I don't see any reason to expose them again. > I would like to have a stable libzmq v4.1 soon because we at Q-Leap > Networks want to use curve for authentication (requires zmq_msg_gets > from 4.1) soon and I would rather have a stable version in the > distribution than a git snapshot. Similary Debian Jessie would benefit > from a new stable libzmq. We can do that at any point. The current master is in very good shape (it pretty much always is, thanks to not allowing people to make big changes). > I wouldn't feel comfortable in rushing a release with czmq merged into > libzmq. We're talking about years here. Heck, the Guide isn't even updated for 4.0 yet. This is one of those rare roadmap / vision threads. Concretely all this has to happen first: - release 4.0.5 sometime very soon - release 4.1.0 RC sometime later - update Guide for 4.1 - release CZMQ v3.0 RC I think CZMQ can be sliced in several ways, e.g. the project modeling should go together with zproto into a new project (I think we agreed on a name but I forget what it was now...). Then libzmq should use that. One thing at a time. -Pieter _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
