-
Notifications
You must be signed in to change notification settings - Fork 60
api: add ConnectionHandler to the connection_pool #210
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
api: add ConnectionHandler to the connection_pool #210
Conversation
391d4e7
to
2a91428
Compare
I put it back in draft to make it easier to review and merge. It will be ready for review after #208 |
f9bad2a
to
77415e3
Compare
To be honest, it makes the whole situation a bit more complicated. When I see the draft, I suppose it's not ready for review. |
77415e3
to
da2b0e5
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'll try to make another iteration after some time
da2b0e5
to
8b54c9e
Compare
be96977
to
ebc71a6
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.
Should be LGTM after resolving this batch of comments.
ebc71a6
to
10e95f1
Compare
10e95f1
to
fac406e
Compare
ConnectionHandler provides callbacks for components interested in handling changes of connections in a ConnectionPool. We have to take into account that user callbacks can take an indefinite amount of time. The simplest solution is to process each connection in a separate goroutine. This should not affect to performance because most of the time these goroutines are blocked. Closes #178
fac406e
to
6dccdd5
Compare
ConnectionHandler provides callbacks for components interested in handling changes of connections in a ConnectionPool.
We have to take into account that user callbacks can take an indefinite amount of time. The simplest solution is to process each connection in a separate goroutine. This should not affect to performance because most of the time these goroutines are blocked.
I didn't forget about (remove if it is not applicable):
Related issues:
Closes #178
The pull request is based on #208. You need to review only a last commit until #208 is not merged.