On Wed, 2014-04-16 at 19:58 +0000, Heyns Emiliano wrote: > So it sounds to me like server initiated syncs will have to be part of > the explanation.
I think that would be better. Note that it'll also cover syncing with phones, which uses the same approach. > If a server initiated sync is conceptually different > from: > > Server: Let's see if I can find Client... Oy, Client! I have contacts > and memos for you! > Client: Bring it! > Server: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Client: OK, got that. Bye! > Server: You still here? That's pretty much it. > then I'd appreciate it if you could point me to some reading that > explains it. Simple preferred, technical OK. There's not much to add. In SyncML, there is a special message that the server sends to the client. It contains a list of pairs of uri (as named in the client) + sync mode, one pair for each database that the client is expected to sync. The client then starts a sync session just as it normally would. In SyncEvolution, a custom method call is used to convey the same information plus some additional details (for example, temporary config changes for the sync, like an increased loglevel). -- 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
