The osaf.us plan calls for Cosmo backup/restore functionality to be developed. (osaf.us is the new, temporary name for the Hosted Service).
Let's say a hard-core server crash of osaf.us happens, and the most recent backups we have are from 3 days ago (more realistically, I'm shooting for backups every 4-12 hours) You, as a Chandler user, have had a busy week and made a lot of changes in the last 3 days. Would you want your server-side data to jump back 3 days in time? What do you think Chandler 0.7a4 will do? Will all the local changes in Chandler be preserved? Or will the "server win" and all your data on the next background sync gets changed to whatever's on the server? It's amusing to think that maybe server-side backups are not a "must have" (except for at least account/username/password data) for Chandler user. If osaf.us does lose all its data, maybe it's better to have people republish? Some key questions: + Do the Chandler desktop devs affirm that server-side backups are still a good thing to have for osaf.us? That is, would you even want your data restored after a server-side crash or would you rather republish yourself? Would you rather have the option? (As opposed to a Cosmo web UI-only user, who would almost assuredly want all available data restored ASAP.) + If we *do* want server-side backups for osaf.us, what's necessary, if anything, to make Chandler behave as well as possible in the event server-side data jumps back in time? + If we include server-side backups, can we add "jump back in time" testing to the ecosystem test plans (if time permits)? -- Jared _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
