-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[mycroft] Adjust thread name for web socket client #14342
Conversation
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.
👍
A counter is maybe not the best option because a new thread pool will be created each time the thing handler is initialized. I see in another binding that |
94b5e6d
to
1c508a9
Compare
@dalgwen : please have a new look. |
1c508a9
to
03e701e
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.
OK for me.
But the whole websocket id construction really seems to be some kind of black magic.
I see that you made some merge request on other bindings for the same purpose.
Shouldn't it be a common method somewhere ?
Like in HexUtils or in UIDUtils ?
It is so easy to not using the thread name properly.
Could make sense to add a method in the same class as the one that provides createHttpClient and createWebSocketClient. |
Awaiting PR openhab/openhab-core#3359 to be merged to then update this PR |
03e701e
to
8845a51
Compare
My initial analysis was wrong, there is no risk of IAE with the current code. |
Signed-off-by: Laurent Garnier <[email protected]>
8845a51
to
6fba25f
Compare
Signed-off-by: Laurent Garnier <[email protected]>
Signed-off-by: Laurent Garnier <[email protected]>
Signed-off-by: Laurent Garnier <[email protected]>
Signed-off-by: Laurent Garnier [email protected]