Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reactor Netty response should not buffer the full response #33781

Closed
rstoyanchev opened this issue Oct 24, 2024 · 0 comments
Closed

Reactor Netty response should not buffer the full response #33781

rstoyanchev opened this issue Oct 24, 2024 · 0 comments
Assignees
@rstoyanchev
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone
6.2.0

Comments

@rstoyanchev
Copy link
Contributor

ReactorClientHttpResponse aggregates the response content to create the InputStream, which is not ideal. Ideally at this level we should be streaming, and allow the choice to buffer or stream depending on the use case. By contrast, we stream for all other supported clients.

Once #31677 is merged, we should be able to use it to enable streaming.
@rstoyanchev rstoyanchev added in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement labels Oct 24, 2024
@rstoyanchev rstoyanchev added this to the 6.2.0 milestone Oct 24, 2024
@rstoyanchev rstoyanchev self-assigned this Oct 24, 2024
@rstoyanchev rstoyanchev mentioned this issue Oct 24, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rstoyanchev rstoyanchev

Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Milestone
6.2.0
Development

No branches or pull requests
1 participant
@rstoyanchev