[maemo-developers] ANNOUNCE: eds-sync released as open-source

[From: Ross Burton]

On Sat, 2007-06-02 at 16:53 +0200, Patrick Ohly wrote:
> When testing SyncEvolution with eds-dbus and the addressbook UI I had
> noticed that contacts deleted via the UI were marked with an X- property
> instead of actually removing them; now it's clear what the intention
> behind that is.
> 
> Would you mind giving some more information why you need this extra
> support instead of simply relying on EDS change markers? Perhaps because
> you need the content of deleted contacts, not just their id?
> 
> So I guess other synchronization software (like SyncEvolution) has to
> support this special property by treating all such marked contacts as
> deleted and then really remove them after a successful synchronization,
> right?
> 
> The drawback is that it difficult to synchronize the Maemo address book
> with both Telepathy rosters and other SyncML servers: one has to take
> care to always synchronize with Telepathy first, then with a SyncML
> server. Otherwise SyncEvolution would remove contacts and thus lead to
> an incomplete sync with eds-sync.

The abook UI will mark a contact as TODELETE with properties if there
are IM fields which need to be removed from a roster first.  Going
online so that this can happen will really remove the contact.  I should
add some documentation to eds-sync to explain what the various field and
contact states are.

Yes, syncing software should respect the contact states.  Going online
before a sync will perform the pending actions, so that will reduce the
severity of syncing contacts with state.

Ross
-- 
Ross Burton                                 mail: ross at burtonini.com
                                          jabber: ross at burtonini.com
                                     www: http://www.burtonini.com./
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF