[core] Fix LocalServer failure to handle large body request (Issue #481)

[sebsto]

Fix #481

[fabianfett]

We should fix this by adding streaming support here.

[sebsto]

@fabianfett Let's separate concerns. This fix handles the incoming data to the local server (what the client sends us)
Let's open a separate issue and PR to fix the outgoing data, i.e. the streaming response

[sebsto]

@fabianfett We need to take a decision.
I understand your preference is to revert back to non NIOAsync implementation of the local server.
But while waiting for this, can we merge this one line change that will unblock #481 ?

Then we can plan for a proper revert to v1 implementation.

[Andrea-Scuderi]

Hey @sebsto and @fabianfett,

Thanks for your work on this! I'm really excited to try out the new runtime and have started experimenting with it.

I've run into a bit of a blocker with this particular issue. Do you have a rough idea of when this PR might be merged?

Also, is there any information you can share about the roadmap for the new runtime? Having a bit more insight would be super helpful for planning and building on top of this awesome package.

Thanks again for all your efforts!

[sebsto]

@Andrea-Scuderi thank you for the encouragement. We’re working on a path to resume development, merge pending PR and tag a 2.0 preview version before the end of the summer

[sebsto]

@fabianfett as this is a blocker for several persons, I decided to move forward by merging this. We can resume the discussion about NIOAsync in a separate issue / PR.

@Andrea-Scuderi heard loud and clear - merged today