Hi,
I had a very simply client and server processes. The server pushes say ~1
GB of data to client. When I used REQ/REP, everything was fine. When I
tried the same program with DEALER/ROUTER, I got seg faults. Can you just
replace REP/REQ with DEALER/ROUTER or are there semantics that are related
Yes, there are differences. The documentation will help you.
cr
On Jun 22, 2012, at 4:39 PM, Diffuser78 wrote:
Hi,
I had a very simply client and server processes. The server pushes say ~1 GB
of data to client. When I used REQ/REP, everything was fine. When I tried the
same program with
Hi,
I just started playing with zmq, and I had a question about HWM.
If my socket type is of ZMQ_REP, and if this socket enters an exceptional
state due to HWM reached, I read in the guide that it will drop the reply
message being sent to the client. *My questions is: would it retry again ?
Can
On Jun 21, 2012, at 11:48 AM, Diffuser78 wrote:
Hi,
I just started playing with zmq, and I had a question about HWM.
If my socket type is of ZMQ_REP, and if this socket enters an exceptional
state due to HWM reached, I read in the guide that it will drop the reply
message being sent to
Thanks, Chuck, for your views and insight on this. I have a fairly newbie
question about the messaging pattern:
In my scenario, App1 (server) pushes say ~10 MB of data to App2 (client)
periodically. In this case, can I make my App1 as REQ and App2 as REP ? In
this communications, App1 is the
On Jun 21, 2012, at 6:23 PM, Diffuser78 wrote:
Thanks, Chuck, for your views and insight on this. I have a fairly newbie
question about the messaging pattern:
In my scenario, App1 (server) pushes say ~10 MB of data to App2 (client)
periodically. In this case, can I make my App1 as REQ and
