netty-reactive-streams icon indicating copy to clipboard operation
netty-reactive-streams copied to clipboard

Consider buffering HTTP request bodies

Open jroper opened this issue 7 years ago • 1 comments

Due to the crossing of thread contexts involved with reactive streams, it can be expensive to process small bodies with a reactive streams implementation, it would be a lot faster if the body was passed along with the HTTP header (as part of the FullHttpRequest). The HTTP streams handler could do this by, if the Content-Length is less than a configured threshold, buffer it and emit it in a FullHttpRequest.

jroper avatar Nov 16 '16 05:11 jroper

Sounds like a great idea

jlouvel avatar Nov 16 '16 19:11 jlouvel