[zeromq-dev] push/pull -- unusual workflow

[Whit Armstrong]

Thanks, Martin.

It was just bad programming and bad debugging on my part.  I did
manage to get this working in most recent version of the rzmq package
(not pushed yet).

I'm going to roll the server portion up into a public ami, so others
can try it out.  It's amazing what one can accomplish in only one
hundred lines of code using zmq.

-Whit


On Mon, Oct 10, 2011 at 6:03 AM, Martin Sustrik <sustrik at 250bpm.com> wrote:
> Hi Whit,
>
>> The problem that I am having is that the pull socket on the client is
>> not receiving all of the results back.  My guess is that the pull
>> socket on the client is attempting to fair queue among the connected
>> workers, and if on worker takes a larger share of the jobs, then
>> potentially the pull socket blocks while waiting for more messages
>> from the other node.  Is that possible?
>
> No. If there are no messages from a particular peer, the fair-queueing
> algorithm simply moves on to the another peer.
>
> If you are missing messages, it's probably a bug. Please, create a minimal
> test case and a ticket in the bug tracker. Thanks!
>
>> Additionally, is it possible to print state information for a socket
>> (I need to determine a good way to prove or disprove this theory).
>
> What kind of state are you interested in?
>
> Martin
>