[
https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135892#comment-13135892
]
Vitalii Tymchyshyn commented on ZOOKEEPER-442:
----------------------------------------------
What I worry about is :
* A group has watch X
* A watch X is deleted, since it's last one - delete watch request is sent to
server. Client watch list is not changed (true?) until ack is received
* A watch Y is added. You must sent add watch request, but how do you know it?
X is still in the list, so it's not empty.
P.S. I must check the code to know time when client watch list is changed. This
can be either request time or ack time. Both ways has it's tricky scenarios.
> 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, 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
