http://bugs.meego.com/show_bug.cgi?id=1359
Summary: server progress events
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: Netbook
OS/Version: IA
Status: ASSIGNED
Severity: normal
Priority: Medium
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
This is from http://bugzilla.moblin.org/show_bug.cgi?id=7709
Description From pohly 2009-11-02 07:45:58 PST (-) [reply]
When the Synthesis engine runs in server mode, it doesn't produce progress
events. According to Lukas, some heavy code refactoring would be needed to get
the progress from the client engine to the shared base class.
The effect on SyncEvolution is that when starting a sync with a phone, our
sync-UI does not show any progress. We also don't show and store statistics. We
want the usage as client and server to be as similar as possible, so we need to
get the progress events into the Synthesis server engine or stop depending on
them.
Perhaps by producing our own events inside the SynthesisDBInterface or a mix-in
class for backends? Refactoring the server code might be easier.
------- Comment #1 From pohly 2009-11-09 12:04:05 PST (-) [reply] -------
Not sure whether it is related: when the sync server session is aborted on the
server side directly after parsing the first message and sending a reply, then
the end status is "sync succeeded". Can be reproduced by running
test-dbus.py TestConnection.testStartSync
The sync session should be recorded as failed, with a suitable error code.
--
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.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues
