-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add TCP_NODELAY #17
Comments
Hi @denyaalt . I didn't have a plan by far, because I don't know what it does. Can you brief me about, in what case and why would people want it? |
TCP_NODELAY disables the Nagle algorithm (disables buffering and delays), which allows data to be sent as quickly as possible. |
@denyaalt Thanks for the explanation, didn't know that. I did a research about Sorry but can you check that too? (If node.js already have that capability I tend to not do it again) |
Yes, this option is available in Node.js when we directly open a TCP socket, I'm not sure if it will work after your wrapper. |
@denyaalt that sounds more like a bug in node.js (unlike SO_REUSEPORT they decided to not support) 🤔 Or, you are welcome to fork this repo and create a local build with |
Hi,
Is it possible to add the TCP_NODELAY setting to SO_REUSEPORT to use them together?
Thanks.
The text was updated successfully, but these errors were encountered: