[maemo-developers] ANNOUNCE: eds-sync released as open-source
From: Patrick Ohly Patrick.Ohly at gmx.deDate: Mon Jun 4 22:30:31 EEST 2007
- Previous message: ANNOUNCE: eds-sync released as open-source
- Next message: ANNOUNCE: eds-sync released as open-source
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 2007-06-04 at 12:15 +0100, Ross Burton wrote: > On Sat, 2007-06-02 at 16:53 +0200, Patrick Ohly wrote: > > 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. I suppose that only happens if eds-sync is installed and configured? That's not the case on my device, so I would still have to check for TODELETE and execute that? If SyncEvolution was started to synchronize and the device goes online for that, isn't there a race condition between eds-sync doing its magic and SyncEvolution accessing the address book? -- Bye, Patrick Ohly -- Patrick.Ohly at gmx.de http://www.estamos.de/
- Previous message: ANNOUNCE: eds-sync released as open-source
- Next message: ANNOUNCE: eds-sync released as open-source
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]