On Mon, Mar 21, 2011 at 5:41 PM, Joachim Bäck <[email protected]> wrote:
> Per runtime/channel (basically a jvm) a corresponding ZMQ.PUB socket is > created. For 0MQ/2.x this is a good approach. With luck 0MQ/3.x will do filtering at the PUB socket, so you can simplify your design when that becomes available. > consumer.svg > Again per runtime/channel (where sonsumers exist for) a ZMQ.SUB socket is > created. Since I know that only messages for a single channel are sent over > the PUB socket I subscribe to "". The messages get forwarded to an inproc > PUB socket and for each consumer a MessageHandler is created. The > MessageHandler connects to the inproc PUB socket and then calls the > corresponding code inside fabric3 to dispatch the event. Sounds fair enough. > I would really like to get your opinion and hope that I dont use zmq in a > wrong way. If you've read the Guide then the chances you are misusing 0MQ will fall considerably. :-) -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
