-
Notifications
You must be signed in to change notification settings - Fork 642
feat: Introduce TcpClientFactory #555
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
base: main
Are you sure you want to change the base?
Conversation
gfoidl
left a comment
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.
custom TcpClient for monitoring and logging
Seems reasonable to me.
A different approach -- more or less a quite big rewrite -- would be incorporate logging, tracing, and metrics into the lib. But that's a lot of work, and older target frameworks won't profit from that change. So your approach seems to be the better way here.
6b30500 to
ba1caa5
Compare
Besides being a bigger rewrite it's also a question of what's needed. I'm not sure if "my" need for logging/metrics would fit a general need or implementation style. So I think it's better to just provide the "possibility". |
gfoidl
left a comment
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.
LGTM -- modulo one comment.
I'd like to hear what the others think about this.
Allows injecting custom TcpClient for monitoring and logging
ba1caa5 to
34b5f6e
Compare
|
Please don't force push a branch when a PR is open, that makes reviewing harder, as the last diff disappears. When merging the PR, then (IMO ideally) a squash-merge is done to get the linear history in the main-branch again. |
|
@gfoidl : any idea when your peers will react? |
Sorry for my late response, awfully busy lately... This seems to be fine, I need to fix the workflows though so GH can also verify it builds. I'll try to get this fixed ASAP. |
Can I support somhow? |
See PR #557. Unfortunately the unit tests don't run reliably, I'm not 100% sure of the cause, but it might be that the tests execute concurrently thus causing the failures. Feel free to chime in. |
Allows injecting custom TcpClient for monitoring and logging