jira-importer commented on issue #535: URL: https://github.com/apache/curator/issues/535#issuecomment-2604692393
<i><a href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=randgalt";>randgalt</a>:</i> <p>>Regarding the WatcherKey, do u see it as a way of wrapping Watcher/CuratorWatcher objects or you think that the recipes should directly use anonymous inner implementations of the WatcherKey?<br/> Yes. The idea is to have a semi-opaque type that isn't accepted in any Curator/ZooKeeper API. This way, the user can't make a mistake. What do you think?</p> <p>Thinking about this more - I wonder if we could hide the WatcherMap altogether inside of Curator. Extend with usingWatcher() semantics to take a WatcherKey instance. This would be translated internally into a WatcherMapped instance. I haven't thought this through. What do you think?</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
