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?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
