Hello, 0mq people. It looks like '1' is a special HWM value.
If it is set for DOWNSTREAM socket, it is never possible to send second message (assuming server side is Ok) via such socket. The behavior is consistent: application blocks on the second send or on poll in case of NONBLOCK mode. I assume the roots of the issue are somewhere near ypipe_t::flush, though not sure. If it is a bug, it is not really important because '1' is rather strange queue length. If it is a feature, the description is appreciated. Thanks. == Best regards and nice weekend, Ilja Golshtein. _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
