https://bugs.meego.com/show_bug.cgi?id=23967
Summary: asynchronous + batched item changes
Classification: MeeGo Projects
Product: SyncEvolution
Platform: ---
Version: unspecified
Platform: Common
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
When making changes to a backend (deleting/updating/adding items), the result
(success/failure + item ID + change tracking information) is expected right
away. That prevents interleaving execution of the change and processing the
next item and batching of multiple changes.
This is bad for performance when the backend needs to talk to some remote
resource (CalDAV/CardDAV server, ActiveSync).
It might be possible to address this by using the delayed item ID resolution
mechanism in libsynthesis. All the intermediate layers (TrackingSyncSource,
MappingSyncSource, APIs) also need to be changed. Finally the backends must be
changed to take advantage of this.
The first candidate for this is the ActiveSync backend where batching changes
would result in a considerable reduction of total sync runtime because of less
network roundtrips.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Undecided
Keywords:
Status: NEW
Who: [email protected]
Assigned To: [email protected]
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=23967
--
Configure bugmail: https://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
