prevent data loss in running activities
tomeu at tomeuvizoso.net
Mon Feb 4 10:20:24 EST 2008
On Fri, 2008-02-01 at 13:41 +0100, Tomeu Vizoso wrote:
> Summarizing, I see three possibilities:
> - Adopt a full-fledged implementation of XSMP and ask activities to
> support just the save-on-shutdown part of it. (Giving a nice wrapper at
> least for python activities).
> - Implement a subset of XSMP in a new session manager implementation.
> - Add a couple of D-Bus methods and signals to OHM/HAL, the sugar shell
> and the activity service enough to support what we need.
One more possibility would be to autosave every X minutes. For
activities using the high level API, we would also need a mechanism for
these to tell the framework if they are dirty.
In this way we minimize further the risk and seriousness of data loss.
Perhaps this would be enough for Update.2?
I understand this is something we want anyway. Eben, am I right?
More information about the Devel