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.

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

Optimize sending requests without a body in RestClient and WebClient with Reactor Netty #34003

Closed
rstoyanchev opened this issue Dec 2, 2024 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@rstoyanchev
Copy link
Contributor

The way we use Reactor Netty when there is no body makes it look to Reactor Netty as if we might send a body, and it causes an extra DATA frame to be sent. We should update our request implementations for Reactor Netty to make it easier to execute the request more optimally.

This was originally raised in reactor/reactor-netty#3524, and there is a change on the Reactor Netty side, see reactor/reactor-netty#3526, to do what they can on their side, but it doesn't address all cases, and we really should improve on our end too.

@rstoyanchev rstoyanchev added in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement labels Dec 2, 2024
@rstoyanchev rstoyanchev added this to the 6.2.1 milestone Dec 2, 2024
@rstoyanchev rstoyanchev self-assigned this Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant