This thread never just never ends... I've written the service definition xml and while doing that found still several things to change. Sorry about that, please bear with me.
Service definition: http://folks.o-hand.com/jku/syncevolution/syncevo2.xml Documentation: http://folks.o-hand.com/jku/syncevolution/index.html Unresolved issues: * Do we want to implement the temporary configuration Patrick suggested? * anything else I may have forgotten? Changes: * GetConfigs: add string params for web url, icon uri and description and boolean consumerready. Description is new compared to existing api. * SessionEnd renamed to SessionChanged (with boolean started) * Removed Ready signal altogether (see below) * StatusChanged and GetStatus: I tried to take the latest discussion in to consideration and modified status values: "not-ready": no 'lock' yet (better name suggestions?) "idle": doing nothing, see error to check if last call succeeded "running": Doing something. source specific status are valid. "aborting" "suspending" These values are valid for specific sources when the generic status is "running": "idle" "running" "done": source has been synced even if whole sync continues Valid modifiers for statuses, e.g. "running:processing" or "suspending;waiting": "processing" "waiting" * remove UpdateConfig, add boolean flag to SetConfig instead * renamed signals Status->StatusChanged, Progress->ProgressChanged * ProgressChanged and GetProgress: Added a string param 'phase' to the source progress structs: "preparing","receiving","sending" or "". * ProgressChanged and GetProgress: Moved sync mode to StatusChanged and GetStatus. I think it makes more sense as state than progress. - Jussi _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
