Re: [Opensync-devel] evolution capabilities

[Graham C. <g+o...@co...>]

On 14/10/13 17:11, Patrick Ohly wrote:
> 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

Interesting.  I think I had missed that (maybe because I hadn't paid any
attention to SyncEvolution until I looked at it as part of Meego, and
Meego was a bit of a special case).

Does it handle syncing between two devices where each stores attributes
the other doesn't know about?  Or does one have to be a superset of the
other?

> 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.

I suppose we will need to think about it for Exchange as well.

Graham