New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConnectionFactory #755
ConnectionFactory #755
Conversation
6ba41a5
to
f71840a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heres some initial feedback
f71840a
to
61c9f92
Compare
a74d193
to
790da92
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not 100% confident this is the best way to organize this state.
My main concern is the multiple clone implementations that clone various internal state, you have to understand the internals of these functions to know which one is the right one to call.
Edit: Oh the new name is clearer, I missed that before.
But the new abstraction does also have some advantages so... LGTM 👍
790da92
to
d2ff5c1
Compare
A change pulled from the
NodePool
PR. No functional changes, just encapsulates the logic for creating new connections.