You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Tom Distler (JIRA)" <ji...@apache.org> on 2015/03/25 16:28:52 UTC

[jira] [Updated] (ZOOKEEPER-2147) Remove ZOO_NOTWATCHING_EVENT

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

Tom Distler updated ZOOKEEPER-2147:
-----------------------------------
          Component/s: c client
    Affects Version/s: 3.5.0

> Remove ZOO_NOTWATCHING_EVENT
> ----------------------------
>
>                 Key: ZOOKEEPER-2147
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2147
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: c client
>    Affects Versions: 3.5.0
>         Environment: All platforms
>            Reporter: Tom Distler
>            Priority: Trivial
>
> A review of the ZK code shows that the NOTWATCHING event is never raised. However, most client users wouldn't know this and would (hopefully) write code to handle the event. We ran into this in our own code, as I refactored some event handling only to find this event isn't going to occur.
> The responses from the community in the following discussion seem to confirm that this event should be removed: http://grokbase.com/t/zookeeper/user/1123dc333d/not-watching-event
> I'm prepared to submit a patch (tested in our load-test environment) if this issue is accepted. I've removed the event completely from all client code (C, Python, etc). One possibility is to leave the event definition in-place, but add a "deprecated" comment so-as not to break existing code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)