[zeromq-dev] ZMQ_FAIL_UNROUTABLE functionality change / BC

Ian Barber ian.barber at gmail.com
Sun Jun 17 09:46:16 CEST 2012

Hi all,

This is re: https://github.com/zeromq/libzmq/pull/383

I just merged in a commit from Andrey that changes the behavior of the
ZMQ_FAIL_UNROUTABLE sockopt - it is renamed to ZMQ_ROUTER_BEHAVIOR (though
with the same value), and now causes an EAGAIN rather than EHOSTUNREACH. I
believe this functionality was only in 3.x, and since we're still on the RC
this may be fine, but this may be a BC break, particularly for any bindings
that were checking for EHOSTUNREACH or referencing the constant.

If we want to keep, but deprecate, the old functionality it would be
straightforward to add a new sockopt with the old name that set
ROUTER_BEHAVIOR to '2' or some unused value, and then triggered the
EHOSTUNREACH instead of EAGAIN. It would be nice not to, but I wanted to
bring it up as I'm not entirely sure 1) whether the old functionality was
in any releases other than the 3.1 RC and 2) whether anyone was using it.
I'm happy to make the patch if anyone is reliant on the old code.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120617/5ec2c40e/attachment.htm>

More information about the zeromq-dev mailing list