I sense another French blog rant is coming soon. :) (just kidding!!!)
cr On Nov 15, 2012, at 7:55 AM, Aurélien Vallée <[email protected]> wrote: > We have exactly the same problem... > Tons of 3.1 pub/sub everywhere, and need to udpate to 3.2 => the whole > architecture has to be update at the same time. Enjoy. > > Can't even build something more robust top of 0mq, since most of the time the > only internal error handling of 0mq is a rough assert. > > > On Thu, Nov 15, 2012 at 12:45 PM, Emmanuel TAUREL <[email protected]> wrote: > Hello, > > On 15/11/2012 13:26, Pieter Hintjens wrote: > > > > So the 3.1 release is problematic, it uses the old wire protocol but > > does subscription upstreaming. The strategy we're using now can't > > recognize this mix. If anyone wants to take a look at the protocol and > > see if there's a solution... > > > > I think we may have to consider 3.1 as an incompatible version. It > > should not have been released as stable with this incompatibility. > > > > > Gasp !! > We have hundred of processes running zmq 3.1 (nicely). > We have started with ZMQ 3.0 which has been made incompatible with ZMQ > 3.1. We moved to 3.1 and now 3.2.1 is incompatible. > > For application users, these incompatibilities generate quite some > trouble and make our life more complicated. > > Regards > > Emmanuel > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > -- > Aurélien Vallée > +33 6 47 41 70 37 > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
