Respect SubscriptionOption.WITH_POOLED_OBJECTS
in PublisherBasedStreamMessage
#3617
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.
…reamMessage`
Motivation:
The implementations of
StreamMessage
in Armeria are in charge of releasing the pooled objectswhen the subscriber subscribes without the
WITH_POOLED_OBJECTS
option.However,
PublisherBasedStreamMessage
currentyly ignoresWITH_POOLED_OBJECTS
option.We should respect that so that the subscriber does not have to deal with when it does not specify
WITH_POOLED_OBJECTS
option.Modifications:
SubscriptionOption.WITH_POOLED_OBJECTS
inPublisherBasedStreamMessage
.WITH_POOLED_OBJECTS
when subscribing does not have to releasethe pooled objects by itself anymore.
Result:
LEAK: ByteBuf.release()
when "server.compression.enabled=true" #3608PublisherBasedStreamMessage
without
WITH_POOLED_OBJECTS
option.