add GossiperMaker, GetGossip(), and UTs #119
Open
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 adds support for custom surrogate Gossiper implementations, as well as the ability to access surrogate Gossip channels.
If a GossiperMaker is not set, or the assigned GossiperMaker returns nil, the default surrogate implementation will be used for that channel.
This change will allow mesh clients to dynamically provision Gossipers for channels instead of defining them all up-front. An example use case would be to use channels as dynamic "namespaces" for data feeds. The data in the feeds could all be the same, or the channel name could indicate what type of data is in the feed. The GossiperMaker could assign different Gossipers to each channel as they are discovered. These channels would be retrievable and usable with the new
GetGossip()
method on the router.