-Re: detecting child changes reliably
Asta, Greg 2013-12-30, 19:39
You could check the version of the nodes or cversion of the parent.
On 12/30/2013 02:15 PM, Jun Rao wrote:
> When a child watcher is fired, it can happen that when the children are
> read, a deleted node is already added back. So, from the list of children,
> it's as if nothing has changed. However, it could be important for an app
> to know in this case that something has changed. I could include some
> metadata per node and read every child node each. However, reading the data
> for every child could be expensive. What's best way to handle this case?