Hi,

  In the ZK programmer's guide, under the section :Things to remember about
Watches, it is mentioned that there is latency between getting the event and
sending new request to get a watch. Usually how much is the latency number??

Thanks
Deepa
--
View this message in context: http://zookeeper-user.578899.n2.nabble.com/Latency-tp7577712.html
Sent from the zookeeper-user mailing list archive at Nabble.com.

I have a case when the node gets updated frequently, and there is a latency
between getting the event notification and re registering the watch on the
same node. During this, the node gets many updates, but the watch is
triggered only for 1 update. Can I actually get all the changes made on the
node?Please comment.

Thanks
Deepa
--
View this message in context: http://zookeeper-user.578899.n2.nabble.com/Latency-tp7577712p7577713.html
Sent from the zookeeper-user mailing list archive at Nabble.com.

You will only get notified once per time when you set a watch. The point of
watches is to indicate that something happened, but the act of that thing
happening needs to be done in such a way for the person notified of the
watch to determine what they need by reading the node or the child
structure or whatever. You can't be guaranteed to receive every action that
happens on a node, as per the documentation.

C

On Tue, Jul 17, 2012 at 9:48 AM, Deepa <[EMAIL PROTECTED]> wrote:

> I have a case when the node gets updated frequently, and there is a latency
> between getting the event notification and re registering the watch on the
> same node. During this, the node gets many updates, but the watch is
> triggered only for 1 update. Can I actually get all the changes made on the
> node?Please comment.
>
> Thanks
> Deepa
>
>
> --
> View this message in context:
> http://zookeeper-user.578899.n2.nabble.com/Latency-tp7577712p7577713.html
> Sent from the zookeeper-user mailing list archive at Nabble.com.
>

No, you cannot get all the changes made on the node.

On Tue, Jul 17, 2012 at 9:48 AM, Deepa <[EMAIL PROTECTED]> wrote:

> I have a case when the node gets updated frequently, and there is a latency
> between getting the event notification and re registering the watch on the
> same node. During this, the node gets many updates, but the watch is
> triggered only for 1 update. Can I actually get all the changes made on the
> node?Please comment.
>
> Thanks
> Deepa
>
>
> --
> View this message in context:
> http://zookeeper-user.578899.n2.nabble.com/Latency-tp7577712p7577713.html
> Sent from the zookeeper-user mailing list archive at Nabble.com.
>