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-138) Unify event listening for NodeCache, PathChildrenCache, TreeCache
Date Mon, 18 Aug 2014 21:53:19 GMT

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

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

Github user cammckenzie commented on the pull request:

    https://github.com/apache/curator/pull/34#issuecomment-52560703
  
    I think we're all in agreement that unifying the 3 cache implementations is the way to
go. What's the way forward to getting it done? Do we just leave PathChildrenCache and NodeCache
as is and depreceate them? Then provide a means for passing a 'max depth' to the TreeCache.
    
    Then, we can just stop maintaining the 2 deprecated caches and ask people to move to TreeCache
if they find issues.
    
    It's not as clean as just reskinning the PathChildrenCache and NodeCache, but it does
give the TreeCache some time to settle.


> Unify event listening for NodeCache, PathChildrenCache, TreeCache
> -----------------------------------------------------------------
>
>                 Key: CURATOR-138
>                 URL: https://issues.apache.org/jira/browse/CURATOR-138
>             Project: Apache Curator
>          Issue Type: Improvement
>            Reporter: Scott Blum
>            Assignee: Jordan Zimmerman
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message