|
From: Chris F. <cd...@fo...> - 2011-12-09 23:49:32
|
On Fri, Dec 09, 2011 at 11:17:16PM +0100, deloptes wrote: > No I have not implemented this yet. I was thinking DataSink should use the > DB API and act as plugin to the synthesis engine, but reading the > documentation I think the UI API is what we need as we are driving the > engine. I believe we need both, if I'm understanding the DB API correctly. We need the UI API to run the engine, and do the sync. But we need the DB API to provide something for the synthesis engine to sync to. i.e. somehow we need to get at the low level contact data, and I'm guessing this is only available via the DB API. If so, then the DB API will be syncing into some database that we can read for when opensync needs to sync to it. osynctool -> Opensync engine -> your_plugin -> UI API -> libsynthesis engine -> ??? -> DB API -> your_libsynthesis_plugin "your_plugin" has access to all of opensync's data. "your_libsynthsis_plugin" has access to the synthesis data. How to make these sets of data meet is the challenge. - Chris |