| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Found with valgrind
|
|
|
|
|
|
| |
This is necessary so we get the actual changeset during replay,
so a mark-as-read action doesn't result in a new mime message, but only
the flag change.
|
| |
|
| |
|
|
|
|
|
|
|
| |
I got failures during a sync during the initial mdb_put that stores the
db name for verification on open (invalid parameter passed).
It seems the verification step actually prevents the problem in the
first place.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Currently only working when creating an entity, the new entity is
always preprended in the store.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
And allow preprocessors to modify the result.
|
|
|
|
| |
clang-format -i */**{.cpp,.h}
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(except for documentation).
|
| |
|
|
|
|
|
| |
This way we don't have to try to figure out whether a change is coming
from the source already.
|
| |
|
|
|
|
| |
removed
|
|
|
|
|
| |
Since we can now inject entity ids we have to ensure they are not
already existing.
|
|
|
|
|
| |
We had quite a bunch of superfluous notifications before (i.e. during
cleanup).
|
|
|
|
|
|
|
| |
Remote id's need to be resolved while syncing any references.
This is done by the synchronizer by consulting the rid to entity id
mapping. If the referenced entity doesn't exist yet we create a local
id anyways, that we then need to pick up once the actual entity arrives.
|
|
|
|
| |
... also if there are intermediate revisions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of having the asynchronous preprocessor concept with different
pipelines for new/modify/delete we have a single pipeline with
synchronous preprocessors that act upon new/modify/delete.
This keeps the code simpler due to lack of asynchronity and keeps the
new/modify/delete operations together (which at least for the indexing
makes a lot of sense).
Not supporting asynchronity is ok because the tasks done in
preprocessing are not cpu intensive (if they were we had a problem
since they are directly involved in the round-trip time), and the main
cost comes from i/o, meaning we don't gain much by doing multithreading.
Costly tasks (such as full-text indexing) should rather be implemented
as post-processing, since that doesn't increase the round-trip time directly,
and eventually consistent is typically good enough for that.
|
| |
|
| |
|
|
|
|
| |
So we can replay the change.
|
| |
|
| |
|
|
|
|
|
| |
So far only includes modifications and additions,
removals are not yet stored as separate revisions.
|
| |
|
|
|
|
| |
Cleanup of revisions, and revision for removed entity is yet missing.
|
| |
|
|
|
|
| |
Adding new types definitely needs to become easier.
|