zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (ZOOKEEPER-50) Watch event delivery rules
Date Wed, 16 Jul 2008 00:07:31 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Patrick Hunt reassigned ZOOKEEPER-50:

    Assignee: Benjamin Reed

Ben can you update the docs appropriately? We should ensure that this is fixed in the java
code -- and that the C code is correct as well.

Assign it to me or Andrew after updating the appropriate docs (or submitting a patch on this
jira if javadoc change required). If you want to fix that would be great too. :-)

> Watch event delivery rules
> --------------------------
>                 Key: ZOOKEEPER-50
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-50
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: java client
>            Reporter: Benjamin Reed
>            Assignee: Benjamin Reed
> We need to make clear in the documentation and enforce in the code the following watch
event rules:
> # A watch event will be delivered once to each watcher, even if it is registered multiple
times. For example, if the same watch object is used for getChildren("/foo", watchObj) and
getData("/foo", watchObj, stat) and foo is deleted, watchObj will be called once to processed
the NodeDeleted event.
> # Session events will be delivered to all watchers.
> *Note: a watcher is a Watcher object in Java or a (watch function, context) pair in C.*
> There is currently a bug in the Java client that causes the session disconnected event
to be delivered twice to the default watcher if the default watcher is also used to watch
a path. This violates rule 1.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message