https://bugs.meego.com/show_bug.cgi?id=20990
Summary: auto sync: determine transport of local sync configs
Classification: MeeGo Projects
Product: SyncEvolution
Platform: ---
Version: unspecified
Platform: Common
Architecture: ALL
Status: NEW
Severity: normal
Priority: High
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Depends on: 20970
Blocks: 20966
Estimated Hours: 0.0
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.
--- Comment #1 from pohly <[email protected]> 2011-07-12 14:32:19 UTC ---
+++ This bug was initially created as a clone of Bug #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;
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: High
Keywords:
Status: NEW
Who: [email protected]
Assigned To: [email protected]
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=20990
--
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.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues
