for this sort of thing, i normally do PUB/SUB from server to clients, and each client does a PUSH back to the server. this rarely loses packets (on teh PUB/SUB) and any lost are covered by the retry logic you need to do in case a client goes down.
On Apr 27, 2013, at 10:34 PM, Feiyi Wang wrote: > hi all, > > I am new to zeromq and very much intrigued by its message pattern support. As > I try to put these concepts into the context of large-scale application for a > mental exercise, I am not sure if I am thinking along the right way. > > Say I have a server/client architecture with a large but relative stable set > of clients (# of client could amount to a million). A frequent need is that > server side wants ALL clients to take certain action and hope for some > confirmation that these actions indeed take place. > > SUB/PUB patterns seems design for cases where it doesn't matter if you miss > some updates, and it doesn't seem to provide any feedback channel for > publisher. > > REP/REQ patterns means that server side needs to maintain a HUGE number of > connections with all clients, and have to wait for responses from all > clients. > > Is there a better way to think or address these issues, or REQ/REP is THE way > for it? > > Thanks > > Feiyi > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev ----------------------- Andrew Hume 623-551-2845 (VO and best) 973-236-2014 (NJ) [email protected]
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
