Adding an option to use a threadpool for Request/Connection processing. #188
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
If HTTP Request processing or TCP connection handling is blocking or is cpu intensive, there isn't a straightforward way to handoff this processing from the channel's eventloop to a different threadpool. This change adds this feature. The examples for TCP and HTTP are added to rx-netty-examples under cpuintensive package.
|
RxNetty-pull-requests #118 FAILURE |
…lete() This caused any errors not getting propagated to the connect() subscriber. Also added some debug for a flaky test.
|
RxNetty-pull-requests #119 SUCCESS |
NiteshKant
added a commit
that referenced
this pull request
Jul 22, 2014
Adding an option to use a threadpool for Request/Connection processing.
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.
If HTTP Request processing or TCP connection handling is blocking or is cpu intensive, there isn't a straightforward way to handoff this processing from the channel's eventloop to a different threadpool.
This change adds this feature. The examples for TCP and HTTP are added to rx-netty-examples under cpuintensive package.