Server/client

[facebookarchive]

Server/client

[jstrizich]

Hi Ernest,
This sounds like a reasonable approach. In response to your questions:

1. fbzmq::NonblockingFlag has to do with reading sockets. Typically you would set this for a socket if you are polling it in an eventloop. If this is set and you read an empty socket, fbzmq will return an error, if not set, the recv will block (timing out or not depending on timeout parameter)
2. If by "enveloping" you mean building multipart messages for something like router-dealer, no, fbzmq does not do any of that for you. we have apis to send and recv multipart messages though.

You may already have read this, but this doc does a nice job outlining router dealer: http://zeromq.org/tutorials:dealer-and-router

John

[kreuzerkrieg]

Thanks for reply.

1. ok, looks like I dont need it at this moment.
2. no, I mean adding identity frames on top of message, I almost sure I dont have to, since the zmq adds it in DEALER/ROUTER case
   So far, everything works as expected until I add second client to send requests. Will keep debugging it

[saifhhasan]

@kreuzerkrieg => Regarding (2) you can refer to ZeroMQ Guide and it should tell you about behaviors as well as multiplexing multiple responses over one ROUTER socket.

fbzmq doesn't modify or introduce any communication pattern behavior between sockets.