|
From: Lukas Z. <lu...@pl...> - 2011-10-25 10:12:51
|
Hello, On Oct 24, 2011, at 23:14 , Chris Frey wrote: > On Sun, Oct 23, 2011 at 12:40:35PM +0200, deloptes wrote: >> My proposal is to discuss it here and I'm asking for input basically to work >> out the design. >>> From the akonadi-plugin experience it is clear what needs to be done on the >> opensync side, so I need some ideas how synthesis can be brought into the >> game. >> >> I was thinking perhaps to take over the syncml library, but it looks like >> there is too much SyncML stuff to care about, which is already done in >> synthesis. >> >> If one of you is interested to assist, please let me know. > > I'm willing to help answer opensync questions and general C and C++ questions > as I am able. I'm not a libsynthesis expert, so I don't have much to offer > in that regard. > > It appears that libsynthesis is also an engine. I don't know if that will > get in the way of turning it into an opensync plugin. You'll have to find > out first if you can use libsynthesis like an API, or whether you have to > use it like a plugin. > > Maybe other people more familiar with the library can answer this. I'm not familiar with Opensync, but I wrote most of libsynthesis. Indeed, libsynthesis is a SyncML engine which has two APIs: - one to use the library in an application to provide SyncML sync (client or server) - another for datastore backend plugins, which are *called* by the engine to read/write/delete data. So the question is if this can fit into the Opensync picture somehow. As libsynthesis was not designed to be integrated as a subsystem of an overall sync architecture as Opensync, it might be difficult. Best Regards, Lukas Zeller, plan44.ch lu...@pl... - www.plan44.ch |