[zeromq-dev] Why signaler implemented via the loopback interface on Windows?

Doron Somech somdoron at gmail.com
Wed Jan 27 13:08:53 CET 2016

Windows is using events for synchronization, however you cannot poll on
both events and handles (sockets), linux is using file descriptors which
are sockets, so you can poll both on file descriptors and sockets. To solve
this on windows pair of tcp sockets are used for signaling only.

So yes inproc is using loopback, but only for signaling (awaking other

SERVER and CLIENT sockets use mutex and conditional variable for signaling.

On Wed, Jan 27, 2016 at 1:58 PM, Ilya Kulakov <kulakov.ilya at gmail.com>

> I'm not experienced in socket programming on Windows, but that seems odd
> there are no better(?) alternatives .
> Does inproc transport rely on the loopback interface on Windows as well?
> Best Regards,
> Ilya Kulakov
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20160127/66db587e/attachment.htm>

More information about the zeromq-dev mailing list