You need to set the identify before the connect, as you did in the Java version.
-Michel
On Thu, Sep 27, 2012 at 8:40 AM, Davis Ford davisf...@gmail.com wrote:
Hi, I'm trying to get some variation of a DEALER / REQ pattern, where the
server (in java) dispatches messages to worker threads.
Ah - brilliant. That fixes it - thanks!
One follow up question, if I try to change the semantics so the client
sends asynchronously, it doesn't seem to work.
In the round-trip example http://zguide.zeromq.org/c:tripping - they do a
loop with both synch and async sending.
If I try the same, the
On Sep 27, 2012, at 11:42 AM, Davis Ford wrote:
One follow up question, if I try to change the semantics so the client sends
asynchronously, it doesn't seem to work.
[snip]
When it gets to the async loop, the program outputs:
Asynchronous round-trip test...
zmq error:: Unknown
Thanks for confirming, Chuck. So, the reason it works for the
http://zguide.zeromq.org/c:tripping demo code is because it is a DEALER
I suspected this, but I'm still experimenting with the API and learning the
semantics.
The FP exception was dump copy/paste from the example code --
On Thu, Sep 27, 2012 at 12:51 PM, Apostolis Xekoukoulotakis
xekou...@gmail.com wrote:
You are printing the frame, not the data.
Also, is java's encoding the same as that of C's?
Maybe this is your problem.
Yea, that was intentional so I could understand how the routing worked --
didn't
