node.js bug with slow socket release workaround #119
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
@see http://habrahabr.ru/post/264851/ The problem is: available socket limit is reached. This workaround solves the problem in some scale.
latest node versions to test
we don't need that shit
…request with a single method supplied. The actual method name requested is given in a first element of the params array in a callback.
- It can be used for cudtom headers manipulation, e.g. setting cookies on the response object
- If promiselib is specified in the options, e.g. `{promiselib: Promise}` and no callback is specified, then methodCall would return a promise.
- And proper fault response generation is implemented with or without code. - Tests and documentation included.
- according to spec: http://xmlrpc.scripting.com/spec.html
MartialSeron
approved these changes
Jul 5, 2017
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.
see http://habrahabr.ru/post/264851/
The problem is: available socket limit is reached. This workaround solves the problem in some scale.