Configurable Multi Channel Chat Support #8
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.
An attempt to write idiomatic go code and better encapsulate subscription and client handling into a dedicated package.
The Idea is to spawn multiple chat channels just by configuring channel name and websocket path in the routes.go file. The idea is to loop through a websocket config collection and using closure to initialize distinct instances for each configured channel, listening to redis messages on the subscribed channels.
This demo helped me a lot to set up chat server on heroku,
I had to extend to support multiple channels to make it work for my use case.
Hope my contribution helps some one who faced the same problem as me.
you can check this medium article for more info : https://medium.com/@rahulroymattam/a-scalable-multi-channel-golang-messaging-server-on-heroku-edf7b236b7ff