Message consumer message delivery reimplementation #5471
Merged
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
vietj
changed the title
|
Some commits for inbound message channel improvements will be moved to a separate PR. |
vietj
force-pushed
the
message-consumer-rework-2
branch
from
030b153 to
1d995b4
Compare
vietj
force-pushed
the
message-consumer-rework-2
branch
3 times, most recently
from
f8dbc61 to
9fd8715
Compare
vietj
force-pushed
the
message-consumer-rework-2
branch
2 times, most recently
from
18d02da to
7d29a9a
Compare
vietj
force-pushed
the
message-consumer-rework-2
branch
from
7d29a9a to
b2e3b0c
Compare
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.
Motivation:
Reimplement
MessageConsumermessage delivery usingInboundMessageChannel.Changes:
MessageConsumeruses now an instance ofInboundMessageChannelto handle message delivery. The dynamic upper bound of buffered messages becomes static to facilitate the implementation. This is a breaking change.MessageConsumerOptionshave been introduced to facilitate the configuration of a consumer, this will be back-ported to 4.5.x, in addition the dynamic buffered message upper bound will be deprecated in that branch.