[jira] Resolved: (ZOOKEEPER-50) Watch event delivery rules

["Mahadev konar (JIRA)" <ji...@apache.org>]

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

Mahadev konar resolved ZOOKEEPER-50.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 3.3.0)
                   3.0.0

this was fixed in 3.0.0


> 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
>             Fix For: 3.0.0
>
>
> 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.