You may want to consider adding a distributed queue to your use of ZK.
As was mentioned previously, watches don't notify you of every change,
just that a change was made. For example multiple changes may be
"visible" when you get the notification.
A distributed queue would allow you to "log" e
Another option besides Steve's excellent one would be to keep something like
1000 nodes in your list per znode. Many update patterns will give you the
same number of updates, but the ZK transactions that result (getChildren,
read znode) will likely be more efficient, especially the getChildren cal
Hi Steve,
While it would be theoretically possible to add the name of the node
that triggered the event to the watcher notification, the problem is
that this may cause you to "miss" events you wanted to see.
ZK does not guarantee you will get an event for "every" change. Any
changes that occur betw
Hi,
I'm interested in being notified by addition/removal of subnode of a
watched node.
The method getChildren allows to be notified when "a successful
operation that deletes the node of the given path or creates/delete a
child under the node". But this notification only provides the path of
the p
