On Thu, 2014-04-24 at 18:35 +0200, Emiliano Heyns wrote: > How are deletes in the file backend distinguished from non-existence > for the purpose of sync? Syncing is not stateless. The backend maintains a list of "file name" + "last modified timestamp" pairs and compares that list against the current information to determine: * new file: exist now, did not exist during last sync * removed file: existed in last sync, gone now * modified file: time stamp is different If that meta information does not exist (anymore), then a slow sync is necessary where all items are treated as new and the engine needs to find pairs between local and remote side. This logic is used by many backends, therefore it is part of the SyncSource.h utility classes. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

On Thu, 2014-04-24 at 21:06 +0200, Emiliano Heyns wrote: > Sweet. Where does this registration live for the file backend, and is > its format documented? Search the ~/.config/syncevolution folder for ".other.ini" and you'll find this meta data. The format is not document for users because they are not supposed to touch these files. Developers can find out more by looking at SyncSourceRevisions (logic) and the ConfigNode classes (for the storage). There are some more dot files and directories (.internal.ini for some config format meta data, .synthesis for SyncML client data, .server.ini for SyncML server data). -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.