[
https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133945#comment-13133945
]
Vitalii Tymchyshyn commented on ZOOKEEPER-442:
----------------------------------------------
OK, as for me:
* On client each watcher group (grouping watchers on path) should have watcher
state - e.g. "normal/deleting/creating"
* Delete watcher message to server must be acked
* If last watcher from group is removed, delete message is sent to server and
watcher goes to deleting state
* As soon as deletion is acked (and group is still in deletion), watcher group
is removed on client
* If new watcher to group is added and watcher group is new or in deleting
state, "watch" message to server is sent and group goes to creating state
* As soon as creation is acked ( and group is still in creating), watcher
group goes to "normal".
> 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
> Assignee: Daniel Gómez Ferro
> 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
