Remove content thread safe from REST layer #10429
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
there is no need for this anymore, for some time, since in netty now we rely on copying over the buffer and reusing it closes elastic#10429
kimchy
force-pushed
the
remove_content_thread_safe
branch
from
7484d14
to
e06dcac
Compare
|
LGTM |
kimchy
added a commit
that referenced
this pull request
Apr 7, 2015
there is no need for this anymore, for some time, since in netty now we rely on copying over the buffer and reusing it closes #10429
clintongormley
added
>enhancement
:Distributed/Network
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
there is no need for this anymore, for some time, since in netty now we rely on copying over the buffer and reusing it