In general, and for as long as the master model remains unchanged, the last input values run by a user will persist from one session to the next. Therefore, if the web browser crashes without a particular set of refined inputs being saved, when the user reconnects to the service these values should re-appear as they were the last time the model was run.
If the original model is updated by the administrator, then any named values explicitly saved by a user will remain available (as long as WebServiceModelConfig.txt continues to expose the same inputs). In contrast, any unsaved values for a given user will be overwritten by the updated original values when they next use the service.
The logic may be extended in the future to allow both server administrator and user to control certain aspects of how the system is initialised on log-in:
- whether a new session should persist previously run inputs or revert to defaults
- a per-model selection of favourite defaults
- a per-model control of whether individual users can choose their own favourites
- a dependent per-user selection of favourite saved inputs (or defaults).