[
https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718915#action_12718915
]
Henry Robinson commented on ZOOKEEPER-442:
------------------------------------------
I think if anything applications are going to use this as a local barrier, so
that they can assume that no watches will be called after the disable_watch
command returns, rather than a remote one that guarantees that no more
notifications will be sent.
It's reasonably hard to guarantee this property, however, as we cannot predict
what the scheduler is going to do, and therefore outstanding watches on the
client may not be scheduled until an arbitrary time after they are supposedly
disabled (because the trigger point comes before the disable command on the
local machine). So maybe it's better not to offer a feature that might be
misunderstood?
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
