On Sun, 2014-04-13 at 07:42 +0000, Emiliano Heyns wrote: > The "Usage" document says this: > > "The target config holds properties > which apply to all sources inside that context, like user name, > password and URL for the server. Once configured, the target config > can be used to list/import/export/update items via the SyncEvolution > command line. It cannot be used for synchronization because it does > not defined what the items are supposed to be synchronized with." > > But username, password and URL are part of the peer, not of the data > source. Is this correct?
It depends. As a special case, the data source can use these three properties as fallback when nothing is set specifically for the source. What that means is that "--print-items @foo source" relies on properties in the source alone (because there is no peer mentioned) but "--print-items target-config@foo source" allows the source to use these extra three properties. I am talking about the behavior as implemented in the WebDAV backend. If I remember correctly, the ActiveSync backend always expects to be used together with a peer and does not support "backendUser/Password" at all. This is only a limitation of the implementation; it would be better if it worked like the WebDAV backend. -- 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
