Users expect an "audit history" or "event history" to check what and when did an event happen (eg chair opened session at 13:57, delegation_1 submitted motion..)
This can be done by creating a new module, apart from the current session module, that is responsible for transcribing valid actions into an event history, along with a timestamp. Furthermore, this module won't use the same websocket connection. Rather, it should output via HTTP to the user requesting history (and perhaps we'll use a caching mechanism on the front to display this info). This also needs to be done due to event history needing to be persistent, and thus, needing different tools than the in-memory system state.
Users expect an "audit history" or "event history" to check what and when did an event happen (eg chair opened session at 13:57, delegation_1 submitted motion..)
This can be done by creating a new module, apart from the current
sessionmodule, that is responsible for transcribing valid actions into an event history, along with a timestamp. Furthermore, this module won't use the same websocket connection. Rather, it should output via HTTP to the user requesting history (and perhaps we'll use a caching mechanism on the front to display this info). This also needs to be done due to event history needing to be persistent, and thus, needing different tools than the in-memory system state.