Reemit "close" and "end" on socket connection #282
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To handle an invalid port I need to listen either to the `close` or to the `end` event during the connection process. The `timeout` event can not be used for such a case: `Emitted if the socket times out from inactivity. This is only to notify that the socket has been idle.` (https://nodejs.org/api/net.html#net_event_timeout)
|
When is this going to be merged? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To handle an invalid port I need to listen either to the
closeor to theendevent during the connection process.The
timeoutevent can not be used for such a case:Emitted if the socket times out from inactivity. This is only to notify that the socket has been idle.(https://nodejs.org/api/net.html#net_event_timeout)