Treat multicast address like loopback address wrt computation of default PublishedEndpoints #3175
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
…ult PublishedEndpoints
externl
approved these changes
Nov 21, 2024
pepone
approved these changes
Nov 21, 2024
InsertCreativityHere
pushed a commit
to InsertCreativityHere/compiler-comparison
that referenced
this pull request
Jan 1, 2025
… address wrt computation of default PublishedEndpoints (zeroc-ice/ice#3175)
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.
This PR updates the default PublishedEndpoints algorithm to treat multicast addresses like loopback addresses, i.e.:
The typical use-case for multicast addresses is naturally a single multicast address. And in this case, the PublishedEndpoints is just this address as-is (+port, interface etc.). We don't want to replace this multicast address by the PublishedHost like we do prior to this PR.