zeromq

I just got started with ZMQ. I am designing an app whose workflow is: one of many clients (who have random PULL addresses) PUSH a request to a server at 5555 the server is forever waiting for client PUSHes. When one comes, a worker process is spawned for that particular request. Yes, worker processes can exist concurrently. When that process completes it's task, it PUSHes the result to the client. I assume that the PUSH/PULL architecture is suited for this. Please correct me on this. But how do I handle these scenarios? the client_receiver.recv() will wait for an infinite time when server

I am currently working on a project that requires some communication over the network of a different data types from some entities of a distributed system and I am using ZMQ. The main goal of the project is to have a central node which services clients which can connect at any time. For each client connected, the central node should manage the message communication between the two. Currently, and by the moment, all communication is happening over TCP. The clients need to send and receive messages at any time so they are ZMQ_DEALER type sockets and the central node is ZMQ_ROUTER Initially, the

Stumble upon reading ZeroMQ FAQ about a Thread safety. My multi-threaded program keeps crashing in weird places inside the ZeroMQ library. What am I doing wrong? ZeroMQ sockets are not thread-safe. This is covered in some detail in the Guide. The short version is that sockets should not be shared between threads. We recommend creating a dedicated socket for each thread. For those situations where a dedicated socket per thread is infeasible, a socket may be shared if and only if each thread executes a full memory barrier before accessing the socket. Most languages support a Mutex or Spinlock