On Wed, Apr 24, 2013 at 8:59 PM, Constantin Asinovski <[email protected]> wrote:

> Would you mind sharing the thinking behind Router socket class? isn't it a
> typical reactor?

A reactor needs to be able to wait on multiple sockets, system file
handles, and timers, at the same time. A router socket is never more
than a part of that. You could wrap the work that applications do into
reusable code but it would sit on top of libzmq and if you did it
fully you'd get something at the same level as Zyre.

-Pieter
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to