|
From: Lukas Z. <lu...@pl...> - 2011-10-27 22:07:23
|
On Oct 27, 2011, at 21:40 , Chris Frey wrote: > On Thu, Oct 27, 2011 at 12:17:40PM +0200, deloptes wrote: >> From my point of view this is doable, also the current libsyncml is doing >> most of the same. I think if no one wants to maintain this library >> libsynthesis can safely replace it. Perhaps there would be some more work >> on the transport stuff, which I saw in SyncEvolution, but didn't have time >> to study. > > I suspect it is technically possible, but it might require some changes > to libsynthesis. :-) Quite some changed, probably. It was designed to be multi-platform, to run a big SyncML server as well as be small enough to run on a Palm V, extendable via subclassing, configurable via XML - but not to integrate as a part of something else (as much I would like to have it that way today). It's pretty monolithic, with lots of dependencies between the internal core classes. > 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. Still, by tuning that local database (which maybe can be reduced to some in-memory data forwarder), there's a lot of access into the data stream when needed. Best Regards, Lukas |