jira-importer commented on issue #535: URL: https://github.com/apache/curator/issues/535#issuecomment-2604692397
<i><a href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=iocanel";>iocanel</a>:</i> <p>> I wonder if we could hide the WatcherMap altogether inside of Curator. Extend with usingWatcher() semantics to take a WatcherKey instance.</p> <p>This would be great. I've experimented with this approach, between the drafts. The problem I run into is that if we have the recipes being completely WatcherMap agnostic, then we can't benefit from close/stop methods that most recipes have and are a good place for returning the "Watcher" back to the pool. So we would have to rely on releasing the Watcher only when fired and I am not sure if this is ideal. An other approach would be to have some short of lifecycle methods on the "WatcherKey" that we could use to release the watcher without referencing the WatcherMap.</p> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@curator.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
