Refine requirements around session pause / resume / export / import #28
Description
We started discussing if we want the ability to explicitly pause / resume a session. A user can pause/resume regardless without our system registering this fact - but having this functionality explicitly means our system would record that fact and include "session pause" / "session resume" event types. Need to think if that would ever be useful to us for any reason, e.g.:
- calculating total session time vs active session time + suspended session time (but we could derive this from timestamps of other events)
- spinning down resources while session is paused or communicating the fact to external systems for whatever reason?
Additionally, we may or may not want is import / export session state and data to/from a dump. We know that sometimes users could start with a grid in one microscope then decide to switch to a different microscope - and even if our system tracked this - the EPU software would loose user experience continuity.
Let's brainstorm here..