http://bugs.meego.com/show_bug.cgi?id=6373
pohly <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #1 from pohly <[email protected]> 2010-09-07 07:59:25 PDT --- (In reply to comment #0) > But the http://syncevolution.org/development/http-server-howto needs to be > adapted so that it actually enables some sources. I think this wasn't already included in the instructions because the "default" template enables sources if it finds the corresponding databases. I probably had all of them available, thus I didn't run into this problem, as you did. Changed the instructions. > Also, the '--source-property sync=?' help text should describe this. '--source-property sync=?' Requests a certain synchronization mode when initiating a sync: two-way = only send/receive changes since last sync slow = exchange all items refresh-from-client = discard all remote items and replace with the items on the client refresh-from-server = discard all local items and replace with the items on the server one-way-from-client = transmit changes from client one-way-from-server = transmit changes from server disabled (or none) = synchronization disabled When accepting a sync session in a SyncML server (HTTP server), only sources with sync != disabled are made available to the client, which chooses the final sync mode based on its own configuration. When accepting a sync session in a SyncML client (local sync with the server contacting SyncEvolution on a device), the sync mode specified in the client is typically overriden by the server. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
