|
From: Patrick O. <pat...@gm...> - 2011-10-28 14:27:12
|
On Fri, 2011-10-28 at 00:07 +0200, Lukas Zeller wrote: > On Oct 27, 2011, at 21:40 , Chris Frey wrote: > > On Thu, Oct 27, 2011 at 12:17:40PM +0200, deloptes wrote: > > Or maybe a large wrapper, which uses libsynthesis > > as intended, to sync into a local database, and then write an > > opensync plugin to sync against that database. > > That sounds like an interesting approach. It'll sure be easier to > implement and debug, and would nicely decouple the different designs. This advantage also has a significant downside: the rest of OpenSync has no idea about the DevInf of the SyncML peer and thus cannot take that into account when reading or writing the local database. It is also not possible to provide the capabilities of the local side to the Synthesis engine because there is not one single peer locally (group concept of OpenSync). As a result, data will get lost when doing round-trip syncs. -- Bye, Patrick Ohly -- Pat...@gm... http://www.estamos.de/ |