This may be helpful: http://api.zeromq.org/3-1:zmq-socket
"*Key differences to conventional sockets* Generally speaking, conventional sockets present a *synchronous* interface to either connection-oriented reliable byte streams (SOCK_STREAM), or connection-less unreliable datagrams (SOCK_DGRAM). In comparison, ØMQ sockets present an abstraction of an asynchronous *message queue*, with the exact queueing semantics depending on the socket type in use. Where conventional sockets transfer streams of bytes or discrete datagrams, ØMQ sockets transfer discrete *messages*. ØMQ sockets being *asynchronous* means that the timings of the physical connection setup and tear down, reconnect and effective delivery are transparent to the user and organized by ØMQ itself. Further, messages may be *queued* in the event that a peer is unavailable to receive them." On Tue, Nov 27, 2012 at 3:40 AM, Martin Hua <[email protected]> wrote: > Hello everybody, > > for my Bachelor thesis I need a synchronous communication for my programm. > > To see how the local IPC communication under zeroMQ operates, I have used > the function zmq_send() and zmq_recv() after the generation of the socket > with ZMQ_REQ and ZMQ_REP. > > After the implementation, I have seen that the communication operates > asynchronous. > > So my question is, whether zeroMQ supports synchronous communication. > I thought that the request-reply Pattern is synchronous. > > I thank you for your answers in advance. > > Best regards, > Martin > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
