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
added noop method unref
to Socket
#1612
Conversation
it has been implemented in node.js 0.9.1 but it's seldomly used. ref: https://nodejs.org/api/net.html#net_socket_unref
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 was going to recommend making it a function that returns the socket, since that's what the real Socket def does for chaining. However, the other three method that use noop
are in the same boat and it probably makes more sense to keep them the same. And we can change them all to return the socket if that need ever arises.
I think it's good as is.
Thanks @zenlor and @mastermatt! |
🎉 This PR is included in version 11.0.0-beta.23 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 11.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
it has been implemented in node.js 0.9.1 but it's seldomly used. ref: https://nodejs.org/api/net.html#net_socket_unref
it has been implemented in node.js 0.9.1 but it's seldomly used. ref: https://nodejs.org/api/net.html#net_socket_unref
it has been implemented in node.js 0.9.1 but it's seldomly used. ref: https://nodejs.org/api/net.html#net_socket_unref
it has been implemented in node.js 0.9.1 but it's seldomly used.
ref: https://nodejs.org/api/net.html#net_socket_unref
I came across this while mocking tests for a project using apm-nodejs-http-client ^