[zeromq-dev] Issue 85 & 92

Pieter Hintjens ph at imatix.com
Sat Oct 16 16:30:38 CEST 2010

On Sat, Oct 16, 2010 at 2:17 PM, Martin Sustrik <sustrik at 250bpm.com> wrote:

> To put it more simply: While your test program is well behaved and doesn't
> migrate the socket, 0MQ has no way to be sure that. If the client happens to
> be Erlang VM or somesuch, it can easily migrate the socket to another OS
> thread without even letting 0MQ know about the fact.

So if you had some API that exotic programs could use to tell
0MQ that they wanted to migrate a socket to a new thread, say
zmq_setsockopt (socket, ZMQ_MIGRATE), this would allow simple programs
to work simply (and zmq_term to work correctly for them), while asking
exotic programs to do extra work.



More information about the zeromq-dev mailing list