On Mon, Dec 12, 2011 at 7:27 PM, Mikko Koppanen <[email protected]>wrote:
> On Mon, Dec 12, 2011 at 6:30 PM, Andrei Zmievski <[email protected]> > wrote: > > I actually don't need to do subscription filtering, but I also don't > want to > > block on HWM, so that's why I was thinking of PUB-SUB model. > > > Hi, > > pub-sub will work for this scenario. If the Java process is something > that can be distributed you could explore PUSH (clients) and PULL > (server) for high-availability and splitting the load. You can still > do non-blocking writes or polling with timeout with PUSH. The other benefit of using PUB/SUB is that you can connect to multiple SUBs if need be, and they can select messages (or get all). This is the reason mongrel2 uses it. Like Mikko says, if you use the noblock then you can just drop messages in HWM state manually without much difficulty, and you'll benefit from knowing that's happened (unlike in the PUBSUB case) - but if you connected multiple PULL sockets, the messages would load balance between them. Ian
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
