Options to use multiple brokers and presence managers #394
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.
A couple of options for Node's Config:
This opens a way to interesting combinations – to inherit various channel options within one setup, opens new ways to scale.
Also, adding a possibility to have Publication.Channel which differs from subscription channel. This opens a road to utilize Broker's wildcard subscriptions. Wildcard subscriptions come with various limitations regarding Centrifuge features - such as join/leave events, presence, history, recovery - those won't work. But at the same time sometimes having a wildcard subscription with at most once delivery is necessary to keep the number of client channels small and thus achive very efficient consuming. I see how this may be especially useful with the addition of
GetBroker
option – because now it's possible to only use wildcards for a specific subset of channels. And still have all Centrifuge features for other channels.