-
-
Notifications
You must be signed in to change notification settings - Fork 21.2k
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
[Net] Removed blocking network address resolution in connect_to_host in websockets #53262
[Net] Removed blocking network address resolution in connect_to_host in websockets #53262
Conversation
f9181ea
to
1b15d86
Compare
fixes #53265 for websocket clients |
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 am deeply sorry for the very long review time, I have been sucked up by the work on the replication API.
This change looks okay, it is a bit of a mess that this has to be handled down in every peer separately, but it's definitely an improvement so I would merge this once the review comments are addressed.
Good work 👍
Vector<String> _protocols; | ||
Vector<String> _original_protocols; |
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 don't understand why we need the _original_protocols
.
It seems there is already the _protocols
variable that could be used.
_connection = _tcp; | ||
|
||
_key = WSLPeer::generate_key(); | ||
// TODO custom extra headers (allow overriding this too?) |
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.
We can remove this TODO since we now support extra headers (was a leftover from the other PR I guess).
Master pr for #53243 (untested)
Bugsquad edit: fixes #53265 for websocket clients