On Thu, 2014-04-10 at 19:45 +0000, Emiliano Heyns wrote: > On 10/04/2014 21:33:05, "Patrick Ohly" <[email protected]> wrote: > >The "sync" property lives in the intersection of data source and sync > >source, so it *is* part of Xmn. I would even say that it is the most > >important part of it, although there are others ("uri", "syncFormat" > >and > >"forceSyncFormat"). > OK, I understand that. But then how should I understand the earlier > "Nothing stops you from setting a "sync" property in one of the Xmn > boxes. But these values are not used and therefore don't make sense > there." when we were discussing how target-config fits into all of this?
You can set a "sync" value there. But SyncEvolution will not use it. Instead it will take the "sync" value from the sync config used to trigger the local sync and override the target-config's "sync" property values accordingly. This is the same situation as with any other property: the config system only knows where each property belongs. It does not know whether a property value is needed or which combinations of values are correct. In other words, the config system knows that "syncURL" can't be set for a source. But it does not know that "databaseFormat" is required when "backend = file" in a particular source config. Another example is the "database" property: it has the same name everywhere, but the actual interpretation depends on the "backend" again. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
