Github user dragonsinth commented on the pull request:
https://github.com/apache/curator/pull/17#issuecomment-50919247
Yes, and I think that's okay. refreshData() should be concurrency safe.
All it does is atomically increment the outstanding ops (so no race there),
then queue up a curator background operation, e.g.
`client.getData().usingWatcher(this).inBackground(this).forPath(path);`
There's no reason this would be a problem, right? path is final so it
won't change, CuratorFramework itself should be thread safe, and if the same
operation happens twice at the same time, the callbacks will still come back in
serial, and the second (duplicate) result should be the same and not produce an
event.
---
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.
---
