ØMQ still seems to follow 2.0 functionality for zmq_close on PUB sockets,
such that in remote_thr the sockets get reaped by zmq_term instead of left
to linger.
Attached is an awful hack to ensure it attains at the time calculated by the
provided rate limit. At least it makes sense even if it is
On 12/02/2010 09:05 AM, Steven McCoy wrote:
ØMQ still seems to follow 2.0 functionality for zmq_close on PUB
sockets, such that in remote_thr the sockets get reaped by zmq_term
instead of left to linger.
Attached is an awful hack to ensure it attains at the time calculated by
the provided
On 2 December 2010 18:17, Martin Sustrik sust...@250bpm.com wrote:
On 12/02/2010 09:05 AM, Steven McCoy wrote:
ØMQ still seems to follow 2.0 functionality for zmq_close on PUB
sockets, such that in remote_thr the sockets get reaped by zmq_term
instead of left to linger.
Attached is an
