[zeromq-dev] Fine control in the ROUTER socket

[Constantin Asinovski]

> In Zyre, we use a ROUTER for incoming messages but send all outgoing
messages on a DEALER, one per peer. This lets us be very precise about e.g.
closing the DEALER socket when we think a peer has died. We use the ROUTER
identity ask key to hold an object per peer, which includes its DEALER socket.


Hi Piter

Doesn't it mean thought that  one has to mirror infrastructure that is
already present inside of the router socket by quite a few users of 0mq?
After all ability to control connections e.g. buffer messages/drop
connections is a common one.

Essentially one has to have extra map with sockets  and extra code that
takes care of all this additional elements. 
Thing you do in ZYRE sounds like a very common use case to me.  Why not to
allow access to underlying components of the router socket instead via some
sort of façade? 

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

Thank you
Constantin