Re: [Opensync-devel] evolution capabilities

[Patrick O. <pat...@gm...>]

On Fri, 2013-10-11 at 11:29 +0100, Graham Cobb wrote:
> To be fair, the capability problem is one of the hardest parts of the
> general sync problem.  In my personal view, opensync has got closest to
> solving it but it still has problems.  That is one of the main reasons I
> have, recently, turned my attention to SyncEvolution, which doesn't even
> try to solve this problem but seems to be good enough in practice.

Actually, SyncEvolution uses a library, libsynthesis, which does have
support for something like capabilities. The library supports tracking
of which properties are supported by each side and ensures that
properties supported only by one side do not get lost. Look for "field
list" in this introduction:
https://syncevolution.org/development/pim-data-synchronization-why-it-so-hard

That and some per-device scripts work fairly well for SyncML devices.
For other kinds of syncing (say, EDS <-> Google via CardDAV) there are
currently no capabilities on the CardDAV side and properties get lost;
I'm working on it, now that Google CardDAV is the main method of syncing
with Google contacts. It wasn't necessary for CalDAV servers.

-- 
Bye, Patrick Ohly
--  
Pat...@gm...
http://www.estamos.de/