Refresh app state after successful save operation

[GrzegorzBednarski]

Problem description:

In order to prevent app inconsistency between the front-end and back-end, we need to make sure the app is refreshed when saved.

Solution:

After successful save operation on the backend - the event should be sent to all listeners (all open WebSocket connections).
The front-end should react to this event by requesting config.json again and reloading the app state.

Acceptance Criteria:

• The Event is sent to all open WebSockets connections
• Changes made on Cogboard opened in browser "A" are reflected on Cogboard opened on browser "B" and vice versa
• We can see the app is calling config.json after The Event was sent on WebSocket
• Page is not reloaded on this event it is just re-rendered

[szymon-owczarzak]

I think we should do this a bit differently.
When config was saved, Instead of refreshing the page backend should send a special event to all listeners (open Cogboards) notifying them that they should refresh.
Refresh should just make a config call again and just reload the app state.

[GrzegorzBednarski]

Agreed

[szymon-owczarzak]

Agreed

In this case, I'm updating the description.