Don't try to wrap socket "onread" when socket is already closed. #15
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.
In order to wrap socket._handle.onread, we hook into the server's 'connection' event with the aim of wrapping the onread function before request handling begins.
However, it is possible that other 'connection' event handlers will run before ours, and they may close the connection before we get a chance to run. In that case, socket._handle is already gone and there is no
longer any onread function for us to wrap, so we just do nothing.
I believe this resolves issue #13.