If the local file has not changed, upload or download depending on local and remote update times.Ĭonflicts may be handled by creating a copy of the file (a la Dropbox): If the local file has changed but the update time in the local database is older than in the server, there is new version in both ends and there is a conflict.Ģ.3.
If a local file has changed (based on md5) but the update time in the local database is the same or newer than in the server, the file has been modified locally and should be uploaded, no matter its modification time is older.Ģ.2. If megasyng is not running, upon startup it should check all the files in the folder, and:Ģ.1.Just for sanity, if the update time at the server differs from the local database, it is a conflict (the file have been modified by another megasync client). If megasync is online, it should detect the file have changed and should upload the new version, even if the modification time of the new version is older than the update time in the database."Update" time is last time megasync has processed the file, not the actual file's modification time. I am switching back to Dropbox because it is too much a risk for me.Ī local database with "update" times of each file (maybe indexed by md5) may do the trick. I do not know how it is done, but Dropbox handles it in the right way, even if Dropbox is not running at the time the file is replaced by the old one. This issue may lead to very disappointing results.
Replacing an existing file by another with the same name but older date/time is a common task.
0 kommentar(er)
