Github user skamille commented on the issue:
https://github.com/apache/zookeeper/pull/136
We have to remember that people who don't use TreeCache will still use this
feature. Not to say that we shouldn't keep it in mind as an important user, but
presumably people who don't actually do anything with curator will decide to
use this feature. Does the design make sense absent that consideration?
Specifically, if you weren't thinking of this as a feature for TreeCache, would
we implement it to automatically watch children changes as well, or would it be
broken up into two modes: persistent no children, persistent children.
---
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.
---
