Client 2 is not guaranteed to see X if it doesn't get to asking before the
value has been updated to Y.

On Thu, Oct 28, 2010 at 2:39 PM, Stack <> wrote:

> Client 2 is also watching the znode.  It gets notified three times:
> two nodeDataChanged events(only) and a nodeDeleted event.  I'd expect
> 3 nodeDataChanged events but understand a client might skip states.
> The problem is that when client 2 looks at the data in the znode on
> nodeDataChanged, for both cases the data is Y.  Not X and then Y, but
> Y both times.  This is unexpected.

Reply via email to