[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Traverso-devel] Incremental backup solution
From: |
Jonatan Liljedahl |
Subject: |
Re: [Traverso-devel] Incremental backup solution |
Date: |
Wed, 03 Oct 2007 23:34:54 +0200 |
User-agent: |
Thunderbird 1.5.0.4 (X11/20060516) |
Remon wrote:
> Hi,
>
> Good points you have here. I've been thinking about a somewhat
> different approach. Since all (well, almost all) actions are
> dispatched via the InputEngine, we could add a 'edit weight' to each
> action. The cumulative edit weight then can be used to trigger a save
> and create backup action, it of course could also be combined with a
> timeout value, if after elapsed timeout time cumulative hasn't
> triggered the threshold, still do a save + backup.
Wow, that sounds pretty advanced. I'm not sure it's worth the effort,
and there's also something I don't like with machines trying to be
"smart", I like when the behavior is simple and well defined. :)
Therefore my vote goes for Nicolas idea below:
>> Backup strategy: - no backups (never create a new project file) -
>> reasonable (only create a new file if the project is loaded) -
>> paranoid (each saving creates a new file)
--
/Jonatan [ http://kymatica.com ]
Re: [Traverso-devel] Incremental backup solution, Nicola Döbelin, 2007/10/03