Re: Client seeing wrong data on nodeDataChanged

2010-10-28 Thread Ted Dunning
On Thu, Oct 28, 2010 at 9:56 PM, Stack wrote: > On Thu, Oct 28, 2010 at 7:32 PM, Ted Dunning > wrote: > > Client 2 is not guaranteed to see X if it doesn't get to asking before > the > > value has been updated to Y. > > > Right, but I wouldn't expect the watch to be triggered twice with value Y.

Re: Client seeing wrong data on nodeDataChanged

2010-10-28 Thread Stack
On Thu, Oct 28, 2010 at 7:32 PM, Ted Dunning wrote: > Client 2 is not guaranteed to see X if it doesn't get to asking before the > value has been updated to Y. > Right, but I wouldn't expect the watch to be triggered twice with value Y. Anyways, I think we have a handle on whats going on: at the

Re: Client seeing wrong data on nodeDataChanged

2010-10-28 Thread Ted Dunning
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