[also shortening the reply a bit ...]
>> But I have to point that keeping the local file with changes in
>> the memory could be a bad idea if the computer or server that hosts
>> Pootle unexpectedly loss the energy supply.
>
> You are right, this feels a little bit scary. But right now I can't think of a
> simple way how to avoid this potential problem. I guess, it would involve
> maintaining a kind of work-in-progress queue - which feels a little bit like
> overkill considering the small probability of this kind of failure.
> Any implementation ideas are warmly welcome, of course!
This could be storing the file in the hard disk and not in the memory
and deleting it after the operation. There is no chance to avoid this,
a copy must be saved during the operation to avoid the loss of data.
Bye,
Leandro Regueiro
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle
