Re: [SyncEvolution] SyncEvolution 1.0 alpha 1: SyncML server, syncs with phone

This will indeed cause duplicate source alerts in SAN but now failing the phone at the moment.

This will indeed cause duplicate source alerts in SAN but *not* failing the phone at the moment.

-----Original Message----- From: syncevolution-bounces(a)syncevolution.org [mailto:syncevolution-bounces@syncevolution.org] On Behalf Of Chen, Congwu Sent: Tuesday, December 08, 2009 10:44 AM To: Ohly, Patrick Cc: SyncEvolution Subject: Re: [SyncEvolution] SyncEvolution 1.0 alpha 1: SyncML server, syncs with phone Patrick wrote: >On Thu, 2009-12-03 at 07:03 +0000, Chen, Congwu wrote: >=> http://syncevolution.org/development/sync-phone > >Some questions about this: > 1. Is setting remoteIdentifier necessary? I remember that you found > it to be unnecessary. As long as we are unsure how exactly > phones identify their peers (MAC address or identifier?), we > might be better of not setting remoteIdentifier and thus using > the unique deviceId instead, to allow syncing the same phone > with multiple desktops. Setting "remoteIdentifier=PC Suite" then > becomes a tip for users of phones which depend on it.... [a bit > later]... you already have it under "trouble shooting", so I > think it can be removed at the beginning. > 2. When enabling "super" datastore, a hint is needed that this does > not yet work as described with 1.0 alpha 1 (MB #8424). As a > workaround, manually creating the source first should do the > trick (mkdir ~/.config/default/sources/super). Accept. > 3. When using a "super" datastore, should the user do > "syncevolution myphone super" or "syncevolution myphone >calendar > todo"? It seems that setting "uri=super" for calendar and todo > makes the later possible, but doesn't that lead to duplicate > entries in the SAN? "syncevolution myphone super" might not work > because "uri" is not set - is that necessary? It is expected to be used by: "syncevolution myphone calendar" to sync with one type or "syncevolution myphone calendar todo" to sync with both. This will indeed cause duplicate source alerts in SAN but now failing the phone at the moment. "syncevolution myphone super" is not working. Perhaps we will also support this? > 4. Troubleshooting "3. Change your database name" -> Change your > URI, right? The local database name remains fixed, only the name > specified via the "uri" property can be changed. Correct! >-- Best Regards, Congwu _______________________________________________ SyncEvolution mailing list SyncEvolution(a)syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution