[zeromq-dev] Peering2 port - no threads, no IPC

[Gregg Irwin]

I'm still working through the guide, and have peering2 almost working.
My language (REBOL) doesn't support threads, and I'm on Windows so no
0MQ IPC scheme either; hence I've made the client and worker threads
into processes, and am using tcp instead of ipc. I've successfully
done lruqueue and peering1 this way already.

Being new to 0MQ, I don't know if I just have a simple bug or if it's
something I don't know about 0MQ that's confusing me.

What happens is that the brokers get the READY messages from workers,
and the IDs look like they're correct in the worker-queue. The client
HELLO messages also come into the broker fine. The broker then sends
the message to a worker, but the worker never seems to get it. i.e.
the worker sends READY, then blocks on recv. If I dump the message
that's going to the worker, the correct worker ID is there, then an
empty string, then the client ID, an empty string, and finally the
body. 

Using 0MQ 2.1.3.

Working through the examples is very helpful, but it will be a while
before I start thinking fluently in messaging patterns. :) For those
in the know, how do you approach debugging on 0MQ, e.g., in situations
like this?

Cheers,

-- Gregg