Hi Pieter, >For inter-process work, it conceivably makes more sense (at least >until you understand 0MQ) to consider sharing a socket between >threads, since one incoming stream may need multiple worker threads. >However the 0MQ answer is to use one thread as distributor, reading >from a frontend socket and forwarding to worker threads on a backend >socket. The Guide has examples of this.
I am having issues understanding how to architect an application correctly using ZeroMQ (I do have a mail about this from yesterday). In my scenario, I have a client (using DEALER socket) connecting to a Server (the server has a ROUTER socket). How would I architect the client, so I can receive messages on the DEALER socket as well as sending messages. My problem is that (as far as I understand), I need to have some sort of loop (poller) to receive messages. By the nature of things, this would most likely run on a separate thread, yes? Then I want to send messages on the same socket. Now I assume I will run into issues with multi-threading and 0MQ (at least that's what my tests do). So how would I solve this the 0MQ way? Niels
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
