On Thu, Oct 28, 2010 at 9:56 PM, Stack <st...@duboce.net> wrote: > On Thu, Oct 28, 2010 at 7:32 PM, Ted Dunning <ted.dunn...@gmail.com> > 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. >
It may not have been. It may have been triggered with the change from x to x, but by the time the client got around to looking when the value was already y. The trigger and the value are not connected.
