On Wed, Mar 21, 2012 at 2:13 AM, Pieter Hintjens <[email protected]> wrote:
> On Tue, Mar 20, 2012 at 9:49 AM, Stephen Hemminger > <[email protected]> wrote: > > > The guide is full of wonderful and useful cases, but there is one that > appears > > to be missing. For some applications there are lots of clients > generating and one collector. > > The clients typically generate data like statistics or information (like > a temperature sensor) > > that occurs periodically. Each message from the client is idempotent > and supersedes > > the last one, therefore it is acceptable for the collector to miss one. > This is sort of > > the inverse of PUB-SUB. > > You can simply use PUB-SUB, where the collector is a SUB, the clients > are PUB, the collector binds and the clients connect. The advantage is > that you can multiple collectors for redundancy. > This is what I use for a simple logging collator. Seems to work well, but we have low throughput at this time. -Luke
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
