[
https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130468#comment-13130468
]
Daniel Gómez Ferro commented on ZOOKEEPER-442:
----------------------------------------------
Are we still interested on this feature after
[ZOOKEEPER-1177|https://issues.apache.org/jira/browse/ZOOKEEPER-1177] gets
integrated?
I have implemented a prototype based on Patrick's suggestion. Issues:
* The removal doesn't guarantee that the watcher won't trigger.
* If the user can specify a concrete watcher to be removed, sometimes we only
have to remove the watcher on the client's side without contacting the server.
If we want the async version of the call we need a mechanism to trigger the
callback directly.
> 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
>
> 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
