Erik, that's correct. You always see the "current" information on the
server, and as part of the request can ask for notification (one time
trigger) of any subsequent change. This guarantees that you won't miss a
change, but multiple changes may occur btw your calls to the get function.
Patric
Avinash Lakshman wrote:
Hi All
Suppose I have a znode, say /Me, and have three nodes A, B and C who have
set watches on this znode. Now suppose some process changes some value on
/Me then watches get delivered to A, B and C. Now if at that instant of time
C were down I could always read the znode
Hi Avinash!
I'm just a beginner so not really sure if I no how everything works, but
this is my understanding of
how watches work.
Setting a watch on node a from client c.
A change to a happens and a notification is sent over to c. The notification
doesn't include any data but just
tells the client
