On Thu, 2009-12-03 at 07:03 +0000, Chen, Congwu wrote: > Patrick wrote: > >I expect that we'll need two HOWTOs: > > * syncing with a phone > > * using SyncEvolution as a HTTP server > > * tuning the Synthesis configuration for specific peers > > > >The first two items should describe configuration and troubleshooting. > >Congwu, can you do the one about local sync with a phone? > Ok, I will make it.
=> 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). 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? 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. -- Best Regards Patrick Ohly Senior Software Engineer Intel GmbH Open Source Technology Center Hermuelheimer Strasse 8a Phone: +49-2232-2090-30 50321 Bruehl Fax: +49-2232-2090-29 Germany _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
