On Sat, 2010-04-24 at 23:29 +0100, Jeffrey Perry wrote: > Apparently the Synthesis library is quite capable in this regard and > so Syncevolution should be robust as well.. provided that 1) (as > mentioned in the second scenario on the page) that the XML that defines > mapping from native to internal synthesis server format is complete and > 2) that the server accurately advertise their capabilities
Right. > I'm still reviewing the source code and getting my head around the > architecture... but I think I'd like to look at the XML and/or > the code segments which advertise capabilities.... I can only speak for the contact backend, as the calendar backend was done by Ove. With contacts in EDS, I know that "contact lists" are not synchronized (http://bugs.meego.com/show_bug.cgi?id=1008). The main reason is that there is no standard format commonly understood between SyncML peers. When using SyncEvolution on both sides, that isn't a problem, and something that works in that combination could be added. On the N900, there are like to be some Nokia extensions which are not synchronzed. I don't know what the situation is with those in Maemo 5, but earlier there were such extensions (http://bugs.meego.com/show_bug.cgi?id=666). > Actually, if someone has reviewed the N900 with HTTP server use case > already, then I might be more assured - perhaps I'm worrying too much. I think you are the first one to look into it in that level of detail. To put you at ease a bit, the automatic database dumps made by SyncEvolution do not pass the data through the Synthesis engine. They take a vCard directly out of EDS and put them into files, so the complete contacts can be restored again should something go wrong. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
