summaryrefslogtreecommitdiffstats
path: root/common/synchronizer.cpp
Commit message (Collapse)AuthorAge
* 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
|
* Fixed build issues with pedantic enabledChristian Mollekopf2017-01-12
|
* syncThen is no longer necessaryChristian Mollekopf2017-01-12
|
* Debug outputChristian Mollekopf2017-01-07
|
* Debug outputChristian Mollekopf2017-01-06
|
* Introduced Log::ContextChristian Mollekopf2016-12-22
| | | | | | | To have hierarchical debug output we have to pass around something at run-time, there is no reasonable alternative. Log::Context provides the identifier to do just that and largely replaces the debug component idea.
* Let the preprocessor repeat the types.Christian Mollekopf2016-12-08
|
* Move mail to sent folder after sending itChristian Mollekopf2016-12-06
|
* Don't reference temporary memoryChristian Mollekopf2016-11-29
|
* The synchronization call can be sync.Christian Mollekopf2016-11-29
| | | | | ... because we really just enqueue the request and then wait for the notification.
* Renamed RemoteIdMap to SynchronizerStoreChristian Mollekopf2016-11-28
|
* Added the flush command.Christian Mollekopf2016-11-25
| | | | | | | Instead of trying to actually flush queues, we send a special command through the same queues as the other commands and can thus guarantee that the respective commands have been processed without blocking anything.
* Ensure we always process the full queue and that flushing works.Christian Mollekopf2016-11-22
|
* Process change replays as part of the synchronization queueChristian Mollekopf2016-11-22
|
* Folded the SourceWriteback into the Synchronizer.Christian Mollekopf2016-11-21
| | | | | | | | | | | | By concentrating all communication to the source in one place we get rid of several oddities. * Quite a bit of duplication since both need access to the synchronizationStore and the source. * We currently have an akward locking in place because both classes access the ync store. This is not easier to resolve cleanly. * The live of resource implementers becomes easier. * An implementation could elect to not use changereplay and always do a full sync... (maybe?)
* Prepared new query based synchronization APIChristian Mollekopf2016-11-11
|
* Implement debug stream operators for query.Christian Mollekopf2016-11-07
|
* Removed EntityReaderChristian Mollekopf2016-10-21
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-29 08:57:57 +0000