[zeromq-dev] Confusion in the parallel pipe example

2013-04-09 Thread Pritesh Acharya
In the parallel pipe example,

zmq_bind (sender, tcp://*:5557);

zmq_connect (sink, tcp://localhost:5558);

and s_send (sink, 0);

s_send (sender, string);

how does the control continues in the first s_send and block on the second
s_send, when I haven't started sink on 5558 port.

?
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev


Re: [zeromq-dev] Confusion in the parallel pipe example

2013-04-09 Thread Pieter Hintjens
Hi Pritesh,

You're talking about the task ventilator?

The second send doesn't block. The task pipeline can be a little
puzzling at first; best thing is to draw the design on paper and try
to understand the message flow from piece to piece.

-Pieter



On Tue, Apr 9, 2013 at 9:56 AM, Pritesh Acharya
priteshacha...@gmail.com wrote:
 In the parallel pipe example,

 zmq_bind (sender, tcp://*:5557);

 zmq_connect (sink, tcp://localhost:5558);

 and s_send (sink, 0);

 s_send (sender, string);

 how does the control continues in the first s_send and block on the second
 s_send, when I haven't started sink on 5558 port.

 ?


 ___
 zeromq-dev mailing list
 zeromq-dev@lists.zeromq.org
 http://lists.zeromq.org/mailman/listinfo/zeromq-dev

___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev