Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (nike.apache.org: domain of Jim.Carroll@navteq.com
 designates 204.120.70.37 as permitted sender)
From: "Carroll, Jim" <Jim.Carroll@navteq.com>
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
Date: Wed, 14 Mar 2012 08:06:52 -0400
Subject: Question about watcher guarantees
Thread-Topic: Question about watcher guarantees
Thread-Index: AQHNAdrxPQU1qD7OjEmLS/Xu3YoUgg==
Message-ID: 
 <1494A31B6C07164EB6B2D2BDFECA19351A34C0C9C9@TRF-EX-MB01.ad.navteq.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


I found two places in the documentation that explain that I can miss change=
 events in watchers due to the "one-time" nature of set watches. This makes=
 sense. However, some of the examples (e.g. Barrier) assume that at least t=
he default watcher will never miss a change event.

Can I safely make that assumption about the default watcher?

If so, can I use the "path" information to avoid the "flood" of clients get=
ting the current state of the node hierarchy? For example, if I assume I wo=
nt miss any events in the main watcher and I get a NodeCreated event with t=
he path, can I simply update my client with that information and assume I'm=
 up to date? This would run contrary to the answer provided for the FAQ que=
stion with the label "Why doesn't the NodeChildrenChanged and NodeDataChang=
ed watch events return more information about the change?"

Thanks
Jim

The information contained in this communication may be CONFIDENTIAL and is =
intended only for the use of the recipient(s) named above.  If you are not =
the intended recipient, you are hereby notified that any dissemination, dis=
tribution, or copying of this communication, or any of its contents, is str=
ictly prohibited.  If you have received this communication in error, please=
 notify the sender and delete/destroy the original message and any copy of =
it from your computer or paper files.