On 31 May 2013 23:58, Joshua Foster <[email protected]> wrote: > I usually implement this with multiple sockets. You can then use the > poller to priorities the messages from another socket. >
This has always been the methodology without native support, quite frequently with TIBCO Rendezvous for example. Common use case has been basic in-band management and monitoring. However I have seen both TIBCO and Reuters add "full priority support" to their platforms via priority queue implementations on send and receive side and both resulted in significant performance hit. The TIBCO side is just over engineered and relies on pools of queues and workers, presumably there must be a case for heavy Java workers to function more elegantly. Reuters side implements fair queuing on priority such that higher priorities will never completely saturate event handling. With multiple ZeroMQ sockets you would naturally have to implement such features oneself as required. -- Steve-o
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
