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 the 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 getting the current state of the node hierarchy? For example, if I assume I wont miss any events in the main watcher and I get a NodeCreated event with the 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 question with the label "Why doesn't the NodeChildrenChanged and NodeDataChanged 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, distribution, or copying of this communication, or any of its contents, is strictly 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.
