[
https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082681#comment-14082681
]
ASF GitHub Bot commented on CURATOR-33:
---------------------------------------
Github user dragonsinth commented on the pull request:
https://github.com/apache/curator/pull/17#issuecomment-50918169
So I looked through the issue you described with respect to
wasReconnected() being called concurrently with refreshData / refreshChildren.
I can't actually see any potential problems with this. None of the code paths
from wasReconnected()/wasCreated()/wasDeleted() perform any mutations, all they
ultimately do is queue up ZK operations which fire on the serialized background
response thread. The background response thread is the only thread that
mutates the tree.
Do you see something I'm missing?
> Recursive Node Cache
> --------------------
>
> Key: CURATOR-33
> URL: https://issues.apache.org/jira/browse/CURATOR-33
> Project: Apache Curator
> Issue Type: Improvement
> Components: Recipes
> Reporter: John Vines
> Assignee: Jordan Zimmerman
> Fix For: TBD
>
> Attachments: CURATOR-33.2.patch, CURATOR-33.patch
>
>
> Currently the PathChildrenCache will trigger listen events for all children
> at the given node. However, it would be useful to have a cache that would
> trigger listen events for the entire hierarchy below the given node.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
