auto sync: determine transport of local sync configs
Submitted by Patrick Ohly @pohly
Assigned to SyncEvolution Community
Description
---- Reported by patrick.ohly@intel.com 2011-07-12 10:42:33 +0000 ----
Auto-syncing of local sync configs probably doesn't work at the moment because they never match the "peer is online" checks in the AutoSyncManager code.
The manager should determine what the peer needs based on peerType. Checking the target config's syncURL doesn't work well because there might not be any.
There also needs to be fallback for "don't know whether it works", in which case syncing should be allowed.
---- Additional Comments From patrick.ohly@intel.com 2011-07-12 14:32:19 +0000 ----
+++ This bug was initially created as a clone of https://bugs.meego.com/show_bug.cgi?id=20970 +++
The manager should determine what the peer needs based on peerType. Checking the target config's syncURL doesn't work well because there might not be any. Right now the code assumes that local:// sync depends on HTTP:
} else if (boost::istarts_with(url, "local")) { // TODO: instead of assuming that local sync needs HTTP, really look into the target config // and determine what the peerType is transport = AutoSyncTask::NEEDS_HTTP;
---- Additional Comments From patrick.ohly@intel.com 2011-07-13 11:01:40 +0000 ----
https://bugs.meego.com/show_bug.cgi?id=20970 is fixed, this one still needs to be dealt with.
--- Bug imported by patrick.ohly@gmx.de 2012-07-29 20:36 UTC ---
This bug was previously known as bug 20990 at https://bugs.meego.com/show_bug.cgi?id=20990 This bug depended on bug(s) 20970.