Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:session-management [2009/07/19 14:44] – add bits about session startup kelnos | dev:session-management [2010/10/02 17:26] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 152: | Line 152: | ||
FIXME: if an app in the Application phase (that was previously saved in the session and is **not** a standard plain-vanilla XDG autostart file) fails to connect to the session manager, do we remove it from the session? | FIXME: if an app in the Application phase (that was previously saved in the session and is **not** a standard plain-vanilla XDG autostart file) fails to connect to the session manager, do we remove it from the session? | ||
+ | |||
+ | ===== Session Saving ===== | ||
+ | |||
+ | ==== Multiple Saved Sessions ==== | ||
+ | |||
+ | As mentioned above, I'm strongly considering removing the feature to have more than one saved session. | ||
+ | |||
+ | ==== Save Session By Default ==== | ||
+ | |||
+ | Assuming session saving actually works properly (I know, big assumption), | ||
+ | - Always save session on logout | ||
+ | - Never save session on logout | ||
+ | - Ask whether to save the session on logout | ||
+ | The third option would obviously display the checkbox in the logout dialog as we do now. We still want to maintain the ability to not save the session, though hopefully this would mainly just be used in kiosk environments where the sysadmin wants the session to start fresh every time it's started. | ||
+ | |||
+ | ==== Checkpointing ==== | ||
+ | |||
+ | Another option migh be a ' |