[zeromq-dev] Important: backward incompatible changes for 0MQ/3.0!

Martin Sustrik sustrik at 250bpm.com
Thu Mar 31 19:26:27 CEST 2011

On 03/31/2011 06:15 PM, Pieter Hintjens wrote:

>> I would say the question is how can we improve reliability of 0mq (NB:
>> not make it perfect, just improve it) without dragging all this madness in.
> Experience of making reliability patterns for the Guide confirms that
> it rapidly becomes madness.
> There's a growing set of high-level patterns that work, though, and it
> would maybe be worth looking at these to see what libzmq could do to
> make it easier. Heartbeating, synchronous connects, more flexible
> req/rep, perhaps. Some simple and widely-useful patterns, like Lazy
> Pirate, could be directly implemented as socket options (that's a
> pattern for REQ that allows it to retry).

Yes, the resend functionality is definitely on my roadmap. However, it 
has to be done properly, i.e. the timeout resend should happen entirely 
in the I/O thread, so that it does not block application thread. There 
are few minor problems associated with that so it'll require some work.


More information about the zeromq-dev mailing list