Context-aware message dispatch on in-memory connector #2374
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
ozangunalp
force-pushed
the
in-memory-context-aware
branch
from
fe23425
to
386fc06
Compare
cescoffier
previously approved these changes
Nov 13, 2023
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.
In-memory connector config and flag for dispatching messages on Vert.x context.
The in-memory incoming channels can configure
run-on-vertx-contextattribute, or setInMemorySource#runOnVertxContextflag during a test for the channel to dispatch events (messages, failure and completion) on Vert.x context. The dispatched messages are wrapped inContextAwareMessageto associate and propagate the message context.MultiUtils.viafor dispatching failure and completion events.