---- Reported by patrick.ohly@intel.com 2010-06-04 05:43:40 +0000 ---- 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... --- Bug imported by patrick.ohly@gmx.de 2012-07-29 20:36 UTC --- This bug was previously known as _bug_ 2670 at https://bugs.meego.com/show_bug.cgi?id=2670
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/9.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.