Hello Congwu, On Nov 10, 2009, at 2:45 , Chen, Congwu wrote:
> I found in SyncEvolution/Synthesis server use case, > "refresh-from-remote" sync is not supported unless we declare > "fromremoteonlysupport" explicitly. > > The documentation about this: > "This is the only sync mode that needs one (or two, if > <synctimestampatend> is enabled) extra timestamps to be maintained > per sync target > " > > Why do we need one/two extra timestamp maintained by datastore in this > use case? Because "from remote only" essentially means that changes on the device side are held back. For the case that the user switches back to a mode that can send changes to the remote party, the engine must know (in addition to the last sync date) the date of the last sync where changes could be transmitted to the remote. However, this should not affect your implementation at all - the DB plugin API was designed for "from remote only" from the beginning and therefore your plugin should work as is. In "from remote only" mode the engine does not query the DB for changes, and when you switch back to normal sync it will query for changes happened since "from remote only" mode was turned on. Best Regards, Lukas Zeller ([email protected]) - Synthesis AG, SyncML Solutions & Sustainable Software Concepts [email protected], http://www.synthesis.ch _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
