Add SPI precedence support and apply for transport SPI #675
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.
Describe what this PR does / why we need it
Add
@SpiOrder
support and apply precedence support for transport SPI (CommandCenter
,HeartbeatSender
).Does this pull request fix one issue?
NONE
Describe how you did it
@SpiOrder
annotation to indicate precedence. Also updateSpiLoader
to support get the SPI with the highest precedence.CommandCenter
,HeartbeatSender
). Two providers now will choose the instance with the highest precedence.Describe how to verify it
Run a demo, put with two different transport modules, then see whether the SPI of higher order is activated.
Special notes for reviews
NONE