Add support for non-blocking HTTP handlers #4
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.
The current design of the HTTP server requires that the HTTP request finishes completely before any other sockets / their requests can be serviced.
For applications where processing an HTTP request may require a (slow) call to an external service, this means that the latency for concurrent calls stacks:
To improve this, add the option for request processors to indicate that the request is processing but not complete yet, allowing the framework to then spin other connections in parallel with the external work: