--- Comment #10 from pohly <patrick.ohly(a)intel.com> 2010-01-28 00:44:02 PST ---
(In reply to comment #8)
(In reply to comment #6)
> 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
what does 'same with change detection' mean here? The backend change detection?
> 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.
how do we detect 'peer is around'? by detecting network and bluetooth presence?
Yes. This works reasonably well for HTTP (assuming the server is up, which it
should be) and not well for Bluetooth, which is why Bluetooth auto sync should
be off unless the user is willing to pay the price of higher power consumption.
> the main view. The main view has:
> * button to sync all shown sources (current "Sync")
> * autosync-toggle per source
> * sync button per source (possibly hidden if autosync is on)
> I'm sure Nick is open for negotiation though...
what about 'interval'? a global option or peer-specific or source specific?
Peer-specific. Different peers may have different needs. In some corner cases
the same might apply to sources, but this is to exotic to warrant the much more
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.