Compatibility

Submitted by Patrick Ohly, updated on 9 Aug 2010 - 13:04

This page summarizes which peers SyncEvolution can exchange data with directly. Through some of these peers (typically web services) it can also synchronize data indirectly, but documenting all of these combinations is beyond the scope of this page. Even for direct peers the lists below are incomplete.

If you want to get a specific peer listed here, be it some other device or a web service, then create a Wiki page and contact the SyncEvolution team.

If you would like to have SyncEvolution tested regularly with a specific server, then you need to provide the following:

  • a description how to configure SyncEvolution for this server
  • an account on the server for the nightly testing
  • help with analyzing any errors that might come up during testing

To get a template for a server into SyncEvolution, please add it as described in the src/README.templates file in the source code. We'll accept pretty much any template as long as it does not set the "consumerReady" flag. Templates with that flag are the ones that show up in the sync-ui, and for those we have additional requirements:

  • Service should be available for normal users, if possible permanently (paid or for free). Time-limited demo servers like my.funambol.com are corner cases, marked with "Demo" in the description.
  • The sync-ui binary contains localized descriptions of some services. We would need something like that for new services.
  • SyncEvolution users of that service should get support from the operator. For us that means that we need a technical contact, ideally someone who has an account on http://meego.com so that we can assign issues to him.
  • Someone should do at least some minimal interoperability testing, ideally using "client-test".

Platforms

SyncML Servers