zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Kornev (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ZOOKEEPER-66) Add NullWatcher, a watcher that does nothing
Date Mon, 07 Jul 2008 03:19:31 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610882#action_12610882

Andrew Kornev commented on ZOOKEEPER-66:

I concur with Flavio: application must implement a watcher. At the very least you'd want to
know about the session events such as connect, disconnect, and especially session expiration
and athentication failure. The latter two cannot be automatically recovered from and must
be handled by the application in a certain way (a new ZooKeeper object must be instantiated).

> Add NullWatcher, a watcher that does nothing
> --------------------------------------------
>                 Key: ZOOKEEPER-66
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-66
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: java client
>            Reporter: Anthony Urso
>            Priority: Minor
>         Attachments: nullwatcher.diff
> I found that I was repeating this code all over the place. Here is a NullWatcher class,
a Watcher that does nothing at all.

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

View raw message