Github user cammckenzie commented on the pull request:
https://github.com/apache/curator/pull/9#issuecomment-45966251
Ok, so what's the way forward? We can either refactor
internalBlockUntilConnectedOrTimedOut() in CuratorZooKeeperClient to allow
arbitrary timeouts, and try to remove the 1 second sleep increments. Or, we can
move the wait logic to the CuratorFramework, and use the
ConnectionStateListener.
Assuming there's not technical reason why the CuratorZooKeeperClient can't
block for arbitrary lengths of time, then it's ok to implement there. I don't
really have a strong preference either way.
---
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.
---
