[zeromq-dev] czmq

[Lucas Hope]

Hi Pieter,

I have a part binding/part re-implementation of cl-czmq -
https://github.com/lhope/cl-czmq .
It supports czmq 1.4.1 and zmq 3.2.3. I have a number of systems in
production which run on it.

Obviously it is well out of date. A few months ago I toyed with the idea of
updating it to czmq 2.x, but many parts were hopelessly broken. I may have
persisted, but it was clear the direction of development had gone even
further towards what you have now released as 3.0rc1. E.G. see the
deprecated list on http://czmq.zeromq.org/page:get-the-software

So my question is, how stable are you intending on keeping the new CZMQ3?
Is it worth binding, or do you suspect it will undergo another large
shakeup in the near future, and hence a lot of work to maintain the binding
- I don't intend to maintain or even include bindings to deprecated
portions of CZMQ.

Cheers,

-Luke



On 15 October 2014 18:09, Pieter Hintjens <ph at imatix.com> wrote:

> OK, I've pushed a CZMQ 3.0.0 release to
> http://czmq.zeromq.org/page:get-the-software
>
> On Wed, Oct 15, 2014 at 2:11 AM, Andrew Hume <andrew at research.att.com>
> wrote:
> > ok, i will do so.
> > can you make a 3.0.0 czmq package and put it somewhere on the website,
> > please?
> >
> > On Oct 14, 2014, at 2:31 PM, Pieter Hintjens <ph at imatix.com> wrote:
> >
> > On Tue, Oct 14, 2014 at 6:54 PM, Andrew Hume <andrew at research.att.com>
> > wrote:
> >
> > (its a pain to switch versions; it was the
> > change in zstr_send that caused me the most annoyance,
> > please don’t do that again — much better to have named
> > the new zstr_send something like zstr_sends (for send string)
> > than to reuse the name.)
> >
> >
> > Ah, this was unfortunate, though we did discuss it (I assume on the
> > CZMQ issue tracker). The zstr_send method and some others accepted a
> > format string, without any indication in the name. This was a security
> > risk and we felt it was better to close that hole and keep the API
> > clean rather than leave the dangerous method there and find another
> > name.
> >
> > Some similar changes in zmsg_pushstr -> zmsg_pushstrf.
> >
> > I apologize, the original poor design was my fault and we should have
> > caught it before 2.0.0.
> >
> > My advice would be to use libzmq 4.0.5 and the current CZMQ master,
> > which will be 3.0.0. It should support the CZMQ 2.x API correctly.
> >
> > -Pieter
> > _______________________________________________
> > zeromq-dev mailing list
> > zeromq-dev at lists.zeromq.org
> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> >
> >
> >
> > -----------------------
> > Andrew Hume
> > 949-707-1964 (VO)
> > andrew at research.att.com
> >
> >
> >
> >
> > _______________________________________________
> > zeromq-dev mailing list
> > zeromq-dev at lists.zeromq.org
> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> >
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>



-- 
---------------------------------------------------
Dr Lucas Hope - lucas.r.hope at skype
Machine Learning and Software Engineering Consultant
Melbourne, Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20141016/32d28350/attachment.htm>