--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2010-01-21 00:33:59 PST ---
(In reply to comment #5)
1. For bluetooth, I learned from discussion on jabber we don't do
auto sync via
it due to the cost of bluetooth.
We can allow the user to do it, but he should be warned that it will be costly
in terms of power. Therefore let's not create special cases for the different
transports if we can avoid it.
2. For network, first check whether the network is up, which depends
Presence checking. If yes, send a package( to be defined) to server and try to
contact it. If getting response as expected, do automatic sync.
Start a sync normally, if we get a response, continue. No special package
needed. For this to work well, we have to make starting a sync cheaper:
- don't dump databases unless a source is active
- same with change detection
See bug #7710 and bug #7708.
3. For USB, we haven't talked about it before. But I think that
it is common to
do sync(device2device, device2pc) via usb cable.
That's a whole different can of worms. Please let's not discuss it here.
Overall, I think it should allow users enabling/disabling automatic
sync in the
We need different configuration options that control the policy which
determines whether an automatic sync is attempted:
- on/off switch per peer
- interval between automatic syncs
- parameters to tune when an automatic sync is possible:
Will the peer be around long enough? Sufficient power left?
I don't think we can predict whether the peer will remain present. We probably
have to use "peer has been around for a configurable duration" as an
approximation for that. Checking power would be nice, but is not essential.
As a next step, these options and thus the underlying policy for automatic
syncs need to be specified in detail.
We also should prevent suspend and power down while a sync runs (any kind of
sync! not just an automatic one!).
So dbus server also have to support this. Any opposition?
All options except for the on/off should have sane defaults, so sync-UI only
needs a single check box and no D-Bus API changes are necessary, because we
only add new properties.
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.