summaryrefslogtreecommitdiffstats
path: root/common/synchronizer.cpp
Commit message (Collapse)AuthorAge
* New Key API in storage layerRémi Nicole2018-07-27
| | | | | | | | | | | | | | | | | Summary: - Use object oriented paradigm for Keys / Identifiers /Revisions - "Compress" keys by using byte representation of Uuids - Still some cleaning left to do - Also run some benchmarks - I'm questioning whether files other than entitystore (tests excluded) are allowed to access this API Reviewers: cmollekopf Reviewed By: cmollekopf Tags: #sink Differential Revision: https://phabricator.kde.org/D13735
* Shouldn't be a warning if we expect to run into it.Christian Mollekopf2018-07-27
| | | | We always run into that when starting a resource.
* Fixed a bunch of warningsChristian Mollekopf2018-05-24
|
* Skip change-replay for already removed entites.Christian Mollekopf2018-05-18
| | | | | This is required to be able to resolve change-replay failures by removing the entity.
* Avoid creating unnecessary rid mappingsChristian Mollekopf2018-05-14
|
* Implement Todo entity typeRémi Nicole2018-05-06
| | | | | | | | | | | | | | | Summary: Some notes: - Needed to specialize some flatbuffers related functions for serializing QStringList and int - Removed useless qWarnings in caldav test - Rename EventSynchronizer -> CalDAVSynchronizer since it also synchronizes Calendars and Todos (and more to come!) Reviewers: cmollekopf Tags: #sink Differential Revision: https://phabricator.kde.org/D12695
* Implement replaying CalDAV events and calendarsRémi Nicole2018-05-03
| | | | | | | | | | | | | | | | Summary: Notes: - For calendars, only removal is implemented because: - There is no DavCollectionCreateJob, possibly because there can't be an empty DAV collection - DavCollectionModifyJob only allows modifying "properties", which we don't use (except for the name, if the name is considered a property) - Currently, modifying an item with Sink overrides the one on the server, even if the store is not up-to-date Reviewers: cmollekopf Tags: #sink Differential Revision: https://phabricator.kde.org/D12611
* Synchronization will fail without it, so warn.Christian Mollekopf2018-03-17
|
* Filtering for empty id's does not work, so detect and guard against it.Christian Mollekopf2018-03-01
|
* One central place to generate uidsChristian Mollekopf2018-01-30
|
* Revert "Fixed warnings"Christian Mollekopf2017-11-12
| | | | | | Doesn't work with CATCH_ERRORS=ON This reverts commit 2bb2a10f5c4010d168b3d26e9937cf26365a0d0c.
* Fixed warningsChristian Mollekopf2017-11-10
|
* Avoid storing the password in the configurationChristian Mollekopf2017-09-18
| | | | | | | The password (or any other secret), is now cached in the client process (in-memory only), and delivered to the resource via command. The resource avoids doing any operations against the source until the secret is available.
* Reduce the number of progress notifications for large sync sets.Christian Mollekopf2017-09-13
| | | | | We don't need an update for every mail if we download 50k mails. We just need enough to animate a progress bar.
* Detect connection lost so we can go to offline stateChristian Mollekopf2017-08-28
| | | | kimap should really have better error codes...
* Default to NoStatus for resources until we know more.Christian Mollekopf2017-08-25
| | | | | | This allows the aggregation to ignore resources where we don't have any status information yet, so the account doesn't always end up being offline.
* CleanupChristian Mollekopf2017-08-11
|
* no need to hardcode thisChristian Mollekopf2017-05-20
|
* Ensure change-replay errors make it through to the correct errorChristian Mollekopf2017-05-20
| | | | handling and are appropriately dealt with.
* Avoid notifcations for requests that do nothing, progress with folderidChristian Mollekopf2017-05-20
|
* Set the resource offline on no serverChristian Mollekopf2017-05-09
| | | | host not found is pretty much the same as offline for our purpose.
* Avoid unnecessary noiseChristian Mollekopf2017-05-04
| | | | Such as progress 0 out of 0 (happens on sync of already synced folder)
* Added progress notificationChristian Mollekopf2017-05-04
|
* Less noiseChristian Mollekopf2017-04-10
|
* Detect maildir resource errorsChristian Mollekopf2017-04-07
|
* Better account status aggregation.Christian Mollekopf2017-04-07
| | | | | | | | | | | | | | | | | | | | | | | Only ever enter error state on non-recoverable errors. Otherwise: * Busy state while busy, then go back to online/offline/error. * If we failed connect during replay/sync we assume we're offline. * If we failed to login but could connect we have a known error condition. * If we succeeded to replay/sync something we are apprently online. At the core we have the problem that we have no way of telling wether we can connect to the server until we actually try (network is not enough: vpns, firewalls, ....). Further the status always reflects the latest status, so even if we were in an error state, once we retry we go out of the error state and either end up back in the error state or not. When aggregating states we have to similarly adjust the state to the most relevant among the resources. The states are ordered like this: * Error * Busy * Connected * Offline
* Fixed changereplay guardChristian Mollekopf2017-04-06
| | | | ...and improved debug output slightly.
* Mailtransport notificationsChristian Mollekopf2017-03-30
|
* CleanupChristian Mollekopf2017-03-28
|
* Only send notifications about being connected if we did somethingChristian Mollekopf2017-03-28
| | | | | | against the source. We used to replay no changes and then claim the resource was online.
* Track the entities that this request applies to directly in theChristian Mollekopf2017-03-28
| | | | | | | | syncrequest That way we can do the notification emitting in the synchronizer and it keeps working even if the login already fails (so the synchronizing code would never be executed).
* Implemented notification support in the model.Christian Mollekopf2017-03-24
| | | | | | | | This will allow us to fold things like progress and sync status directly into the model. Usecases are mail download progress and folder sync progress. Ideally we would also solve the resource/account state through this.
* Make error codes part of the applicationdomain interfaceChristian Mollekopf2017-03-20
|
* emitNotification functionChristian Mollekopf2017-03-17
|
* Debug outputChristian Mollekopf2017-03-14
|
* An error should not stop the synchronizer from processing.Christian Mollekopf2017-03-14
|
* Addressbook supportChristian Mollekopf2017-03-09
|
* Merge synchronization requests for individual mails of the same folder.Christian Mollekopf2017-03-07
| | | | | We use this frequently when loading conversations, so this results in a significant preformance improvement.
* Port away from syncStartv0.1.0Christian Mollekopf2017-03-02
|
* Debug outputChristian Mollekopf2017-02-20
|
* make contacts suitable for applications like sinkshSandro Knauß2017-01-30
|
* Readable uuidChristian Mollekopf2017-01-23
|
* Ensure we don't accidentally spawn more transactions than necessary.Christian Mollekopf2017-01-23
|
* Debug outputChristian Mollekopf2017-01-23
|
* Process sync requests one by oneChristian Mollekopf2017-01-23
|
* Support dependencies between sync requests.Christian Mollekopf2017-01-22
| | | | | | | | | | If one sync task depends on the previous sync task we want to flush in between, so we can query for the results of the previous sync request locally. If we detect such a dependency we temporarily halt all processing of synchronization requests until the flush completes, so we can continue processing.
* Debug outputChristian Mollekopf2017-01-18
|
* Don't overwrite the first job with the continuationChristian Mollekopf2017-01-18
|
* Avoid unnecessary replay requests.Christian Mollekopf2017-01-17
| | | | A single request will replay until the latest revision.
* Handle errors without crashing.Christian Mollekopf2017-01-17
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-28 21:16:16 +0000