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
Self-explanatory. Could work via a WebSocket connection established at page load.
A possible architecture would be this :
Notification object, source: NotificationSource, target: User / targets: Set<User>
NotificationSource interface for Resource objects that can fire notifications, i.e. articles, comments ...
notify() function on User that stores the notification in DB and finds an open WS connection to notify connected clients for the particular user(s) (notifications sent to multiple users might exist in the future)
Fetch all notifications from DB on WS open ...
WIP. More details to be added, esp. in regard to supporting Actions i.e. REPLY that would fire notifications automatically when the Actions framework is implemented.
The text was updated successfully, but these errors were encountered:
Self-explanatory. Could work via a WebSocket connection established at page load.
A possible architecture would be this :
Notification
object,source: NotificationSource
,target: User
/targets: Set<User>
NotificationSource
interface forResource
objects that can fire notifications, i.e. articles, comments ...notify()
function onUser
that stores the notification in DB and finds an open WS connection to notify connected clients for the particular user(s) (notifications sent to multiple users might exist in the future)WIP. More details to be added, esp. in regard to supporting
Actions
i.e.REPLY
that would fire notifications automatically when theActions
framework is implemented.The text was updated successfully, but these errors were encountered: