curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-120) NodeCache and PathChildrenCache should not perform writes
Date Thu, 10 Jul 2014 22:26:05 GMT

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

Scott Blum commented on CURATOR-120:
------------------------------------

I think I may need to just abandon this effort then.  Supporting both modes increases the
testing burden and the number of states the caches can be in.  PathChildrenCache in particular
already has a ton of constructor arguments, I don't really want to make it worse.

So maybe I'll just work on TreeCache as a new thing and have it not autocreate the root node.
 It's simple enough for any clients to manually ensure the node while constructing the recipe.

> NodeCache and PathChildrenCache should not perform writes
> ---------------------------------------------------------
>
>                 Key: CURATOR-120
>                 URL: https://issues.apache.org/jira/browse/CURATOR-120
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>            Reporter: Scott Blum
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> NodeCache and PathChildrenCache should act as read-only views of data.  Unnecessarily,
both of them forcibly create the node being watched.



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

Mime
View raw message