[Syncevolution-issues] [Bug 2670] New: handle server limitations (Google refresh-from-client, suspend/resume)

http://bugs.meego.com/show_bug.cgi?id=2670 Summary: handle server limitations (Google refresh-from-client, suspend/resume) Classification: MeeGo Projects Product: SyncEvolution Version: unspecified Platform: All OS/Version: --- Status: ASSIGNED Severity: enhancement Priority: Undecided Component: SyncEvolution AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: patrick.ohly(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-default-bugs(a)meego.bugs Estimated Hours: 0.0 There are several features which do not work or are not safe to use with certain peers: * Google does not support refresh-from-client, leading to a (for a user) strange error message. * Uncertain which servers fully support suspend/resume. * Funambol does not handle message resends reliably (sending a message again which was already processed by the server confuses the server). This is an incomplete list, there may be other cases. The last point is currently handled by disabling the retry feature in the Funambol config. What we need is some way of documenting these limitations in machine-readable format so that GUIs can present them to the user. We need to take into account that these limitations may get fixed at some point. Either we update them in a SyncEvolution update (implies that we cannot copy them into user configs), make them depend on the server version (thus won't know about those which apply without syncing) or tell the user to update his config in release notes. Open for suggestions... -- Configure bugmail: http://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.