| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
| |
This had a significant performance impact when i.e. syncing a folder
with 10k messages.
|
| |
|
|
| |
The old implementation would result in endlessly nested calls.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of a single #define as debug area the new system allows for an
identifier for each debug message with the structure component.area.
The component is a dot separated identifier of the runtime component,
such as the process or the plugin.
The area is the code component, and can be as such defined at
compiletime.
The idea of this system is that it becomes possible to i.e. look at the
output of all messages in the query subsystem of a specific resource
(something that happens in the client process, but in the
resource-specific subcomponent).
The new macros are supposed to be less likely to clash with other names,
hence the new names.
|
| | |
|
| | |
|
| |
|
|
|
| |
Otherwise we would never replay changes that failed because we were
offline or so.
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
changereplay and synchronization.
This cleans up the API and avoids the excessive passing around of
transactions. It also provides more flexibility in eventually using
different synchronization strategies for different resources.
|
