On Wed, Mar 14, 2012 at 12:50 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
> > This means there's not really any way to avoid the "flood" of client
> get-state requests (getData/getChildren/exists) that will happen when a
> change triggers a watcher. In your example a getData call will happen in
> every client at step (2) whenever a change happens. There's no way to avoid
> it. I'm Ok with that, it's just that the documentation (at some place I
> cant seem to find now) says to try to avoid this.
> See the recipes page for some examples of how to avoid herd effects.
> Sometimes it's possible, but not always:
I would add that sometimes it is important, but not always.