You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2019. It is now read-only.
by getOrCreate() because the latter provides a more descriptive name of the method contract. On the other hand, we should avoid to break any client code so I'd propose the following steps:
Mark get() methods as @deprecated, followed by "Use getOrCreate method instead."
Insert the respective getOrCreate() methods and move the logic from get() to getOrCreate().
Make get() just delegate to its respective getOrCreate() method.
Update the tests and javadoc so that it can now reflect this change.
After those changes, the method get() can be removed in the future without leaving broken client code on the way AND we the class may have a method that better describes its result (the first time I read it, I didn't assume it would create a ZK connection, only after reading the javadoc and source code I saw this).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'd like to suggest the replacement of
http://twitter.github.com/commons/apidocs/com/twitter/common/zookeeper/ZooKeeperClient.html#get()
by getOrCreate() because the latter provides a more descriptive name of the method contract. On the other hand, we should avoid to break any client code so I'd propose the following steps:
After those changes, the method get() can be removed in the future without leaving broken client code on the way AND we the class may have a method that better describes its result (the first time I read it, I didn't assume it would create a ZK connection, only after reading the javadoc and source code I saw this).
The text was updated successfully, but these errors were encountered: