You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discourse uses message_bus to provide real-time notifications. We want to leverage this in our Header, for both Sessions (ex: single logout) and updates.
The flow we are expecting to implement is the Header connecting via message bus to the same channels where Discourse sends notifications to the current logged in user, this way achieving the same reactivity Discourse has in all of our apps.
As part of the research, we expect to define:
How message_bus works in Discourse.
How to connect from other services to message_bus using the current user credentials.
What events we need to listen from message_bus and how we will process them in our Header to achieve the same functionality Discourse has for notifications.
How we can leverage message_bus to implement our own notifications.
Acceptance criteria
Research how we can connect and receive events from Discourse via message_bus
The text was updated successfully, but these errors were encountered:
Discourse uses message_bus to provide real-time notifications. We want to leverage this in our Header, for both Sessions (ex: single logout) and updates.
The flow we are expecting to implement is the Header connecting via message bus to the same channels where Discourse sends notifications to the current logged in user, this way achieving the same reactivity Discourse has in all of our apps.
As part of the research, we expect to define:
Acceptance criteria
The text was updated successfully, but these errors were encountered: