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

[RESTEASY-3015] Avoid a payload byte[] copy when using reactor-netty HTTP client engine #2910

Merged
merged 6 commits into from Sep 23, 2021

Conversation

jamezp
Copy link
Contributor

@jamezp jamezp commented Sep 23, 2021

Ported from #2902

Samuel Cox and others added 6 commits September 23, 2021 08:11
1. Some memory copying is avoided by directly connecting resteasy's
   request payload to the reactor-netty's 'outbound'.
2. Fix a bug where headers added by things like RestEasy
   MessageBodyWriters are appropriately added to the request that
   reactor-netty sends out.
3. If empty due to thread switching, establish ResteasyContext that has
   the Provider->ClientConfiguration such that Provider field level injection
   will work in when the request body is written.

Much credit for these changes is owed to @anilgursel and @dnagarajan89.
And switch to a non-mutating injection technique.
Avoiding this was the main reason we started this work.
Co-authored-by: dhanagarajan <dhanagarajan@paypal.com>
…t-reactor-netty module. (#9)

* Fixed PR comments

* Moved TrackingMap and TrackingClientRequestHeaders to resteasy-client-reactor-netty module.

Co-authored-by: dhanagarajan <dhanagarajan@paypal.com>
@jamezp jamezp merged commit 58ce031 into resteasy:main Sep 23, 2021
@jamezp jamezp deleted the RESTEASY-3015 branch September 27, 2021 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants