Summary: "sync" property: create unambiguous aliases
Classification: MeeGo Projects
Estimated Hours: 0.0
"from-server" and "from-client" in config and command line are problematic
because users do not expect that, for example, in syncing with devices or local
sync with remote CalDAV services the local data is "the server".
Proposal (from "[SyncEvolution] Multi-point sync"):
> $ syncevolution --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-remote = discard all local items and replace with
> the items on the peer
> refresh-from-local = discard all items on the peer and replace
> with the local items
> one-way-from-remote = transmit changes from peer
> one-way-from-local = transmit local changes
> disabled (or none) = synchronization disabled
> refresh/one-way-from-server/client are also supported. Their use is
> discouraged because the direction of the data transfer depends
> on the role of the local side (can be server or client), which is
> not always obvious.
> 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 overridden by the server.
MeeGo Release: unspecified
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.