Message Routing Improvements #1205
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
…oses GH-1165. Closes GH-1130. Closes GH-1087. Closes GH-1050 Adjusting the mechanism for how "sticky" message routing works so that you can have a mix of sticky and not sticky local handlers. Ick. New MultipleHandlerBehavior.Separated flag for "automatic sticky" handlers Ability to make conventional local routing be additive with external message brokers to External transport routing conventions are "sticky handler" aware now
jeremydmiller
changed the title
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.
…oses GH-1165. Closes GH-1130. Closes GH-1087. Closes GH-1050
Adjusting the mechanism for how "sticky" message routing works so that you can have a mix of sticky and not sticky local handlers. Ick.
New MultipleHandlerBehavior.Separated flag for "automatic sticky" handlers
Ability to make conventional local routing be additive with external message brokers to
External transport routing conventions are "sticky handler" aware now