curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-33) Recursive Node Cache
Date Thu, 31 Jul 2014 18:23:40 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081233#comment-14081233
] 

ASF GitHub Bot commented on CURATOR-33:
---------------------------------------

Github user Randgalt commented on the pull request:

    https://github.com/apache/curator/pull/17#issuecomment-50798327
  
    I need to spend more time on this, but I'm suspecting that the refresh*() and was*() methods
of TreeNode need to be synchronized. These methods can be called from the watcher/async callbacks
as well as Curator's connection state listener callback. The watcher/async are from a single
thread in ZK, but Curator's connection state listener callback is a different thread. Thus,
these methods could be called at the same time from two threads (via wasReconnected()).


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

Mime
View raw message