I'm pretty sure that's exactly what happens. ZMQ handles all of the buffering in the background so your application can look clean and good.
Check out this question, fielded by Pieter himself: http://stackoverflow.com/questions/10528659/what-is-the-rationale-behind-zeromq-context On Tue, Mar 10, 2015 at 10:31 PM, Fan Yang <[email protected]> wrote: > Hi, > > I'm not sure about how zmq works asynchronously. Assume that I have two > peers A and B. A has a PUSH socket and B has PULL. Then A connects to B. > > What if A send some messages to B but B hasn't invoked recv() yet? Will > the messages be first received by the zmq IO thread, and then presented > when B starts to recv()? > > Best Regards, > Fan > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
