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
Once #81 is done, we should reuse the web socket client to display notifications.
This may require we rework our in-memory model. Indeed, everytime we change the page, we reload from the server all the information. Except that notifications are not (and will probably not) be stored on the server side. They will be propagated to clients on the fly.
So, rather than loading from rest services everytime, maybe we should store our model in memory and update it when necessary. What we may keep in memory is the list of applications and the associated notifications. Other parts may be loaded on the fly.
The text was updated successfully, but these errors were encountered:
Once #81 is done, we should reuse the web socket client to display notifications.
This may require we rework our in-memory model. Indeed, everytime we change the page, we reload from the server all the information. Except that notifications are not (and will probably not) be stored on the server side. They will be propagated to clients on the fly.
So, rather than loading from rest services everytime, maybe we should store our model in memory and update it when necessary. What we may keep in memory is the list of applications and the associated notifications. Other parts may be loaded on the fly.
The text was updated successfully, but these errors were encountered: