[
https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133915#comment-13133915
]
Daniel Gómez Ferro commented on ZOOKEEPER-442:
----------------------------------------------
How should we deal with the asynchronous version of the call? I see three
options:
* Don't provide an async version.
* Remove the Watcher parameter, effectively removing all watches on the given
znode.
* Find a way to trigger the callback directly from the client (could also help
ZOOKEEPER-847, where we want to throw an exception and invoke the callback)
> need a way to remove watches that are no longer of interest
> -----------------------------------------------------------
>
> Key: ZOOKEEPER-442
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-442
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Benjamin Reed
> Priority: Critical
> Attachments: ZOOKEEPER-442.patch
>
>
> currently the only way a watch cleared is to trigger it. we need a way to
> enumerate the outstanding watch objects, find watch events the objects are
> watching for, and remove interests in an event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
