rabbit_networking: Support systems with distinct listeners for IPv4 and IPv6 #14741
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.
Why
If the system uses distinct listeners for IPv4 and IPv6, the functions listing or stopping listeners would crash because they assumed that the system would listen implicitly to IPv4 when starting an IPv6 listener. This is a common Linuxism.
How
The code now understands that a given protocol can have several associated listeners.
The name and return value of several exported functions changed to reflect that they work on several elements or return a list of elements. Therefore it is a breaking change for plugins relying on these functions.