I think it's crucial to understand when to bind (one waiting on sth.) or when to connect (many awaiting sth.).
You actually made a pipeline example where the (one) PULL worker is bound and the (or multiple) PUSH workers are connect'ing to their sockets.
On the other side, the test program in nanomsg shows an example where the (one) PUSH worker is bound and the (or multiple) PULL workers are connect'ing to their sockets.
In a NNanomsg multi REQ/REP example (not just a MsgPack test) using nn_device (RAW REP, RAW REQ), I'm connecting REQ and also connect'ing the REP socket (to their respective bound RAW sockets).
Discovering this by learning in doing, I believe this is crucial to understand nanomsg!
I think it's crucial to understand when to bind (one waiting on sth.) or when to connect (many awaiting sth.).
You actually made a pipeline example where the (one) PULL worker is bound and the (or multiple) PUSH workers are connect'ing to their sockets.
On the other side, the test program in nanomsg shows an example where the (one) PUSH worker is bound and the (or multiple) PULL workers are connect'ing to their sockets.
In a NNanomsg multi REQ/REP example (not just a MsgPack test) using nn_device (RAW REP, RAW REQ), I'm connecting REQ and also connect'ing the REP socket (to their respective bound RAW sockets).
Discovering this by learning in doing, I believe this is crucial to understand nanomsg!