[
https://issues.apache.org/jira/browse/CURATOR-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126813#comment-15126813
]
Chris Conroy commented on CURATOR-296:
--------------------------------------
[~dragonsinth] has a branch for this:
https://github.com/dragonsinth/curator/tree/scottb/treecache-reinit
I also started work on a branch that fires a different since reusing the
INITIALIZED event for this may confuse some existing listener implementations.
> Notify cache listeners when re-init completes after reconnect
> -------------------------------------------------------------
>
> Key: CURATOR-296
> URL: https://issues.apache.org/jira/browse/CURATOR-296
> Project: Apache Curator
> Issue Type: Improvement
> Components: Recipes
> Reporter: Chris Conroy
> Priority: Minor
>
> The cache recipes notify listeners when the cache has finished materializing
> the subtree it is responsible for with an INITIALIZED event.
> Listeners are also notified of connection loss and reconnect. However, a
> listener should also be notified of the subsequent re-initialization after a
> reconnect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
