[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718577#action_12718577
 ] 

Patrick Hunt commented on ZOOKEEPER-442:
----------------------------------------

we must be careful to clearly define/implement the semantics of removing a 
watch. for example watches may have been
triggered and a notification delivered to the client but not yet processed by 
the client - it's waiting in the event queue. etc...
what are we removing? the trigger or both the trigger and notification(s)? what 
if one client has been notified but not 
others (say two clients watch a node N, c1 is on a fast server and gets 
notified, c2 removes the watch on a slow server
before the trigger fires, ...) etc...

it would be great if someone was willing to document a proposal(s) and post it 
on this jira for review/comment. once
we have something clearly defined/agreedupon it shouldn't be too hard to 
implement. (hah! :-) )


> 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.

Reply via email to