BCU sends all information on any update. Frontend decides what to do with the information
upside: easy
downside:
much data is sent around
hard to keep overview on who needs what
ping/request model
BCU sends signal to indicate that something has changed
Fronend may ignore it or request new values
Mixture
general data is loaded at page load
other data can be dynamically requested
Polling
backend never sends on it's own
frontend has to request everything
no.
Subscribing
frontend sends message: client has connected and has this list of info it needs to be up to date
backend sends info in list immediately and
backend subscribes the whole list on behalf of client
backend notifies frontend if state changes
Decision
we go with model 1: Backend/BCU sends message for each update (KISS). In other words. Every update is being sent directly to UI. Maybe some closely related messages will be sent in a single message.
Send all state information on page load and tab change
M-Welsch
commented
1 year ago
Requirements
Ideas
Decision
we go with model 1: Backend/BCU sends message for each update (KISS). In other words. Every update is being sent directly to UI. Maybe some closely related messages will be sent in a single message.
Send all state information on page load and tab change
Messages are (nested) json strings.