| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
This removes one dependency from the Listener and will allow us
to test the Listener better.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Simpler api, GenericResource didn't honor size anyways,
and we copy the command for now to avoid sideeffects of data coming in
in the meantime (although that should generally work since data is
always appended).
|
| |
|
| |
|
| |
|
|
|
|
| |
With equality filter on arbitrary properties as a bonus.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The queryrunner is responsible for running queries and keeping them
up to date. This is required for self-updating queries.
To get this to work properly the ResultProvider/emitter had to be fixed.
The emitter now only lives as long as the client holds a reference to
it, allowing the provider to detect when it is no longer necessary to
keep the query alive (because noone is listening).
In the process various lifetime issues have been fixed, that we're
caused by lambdas capturing smartpointers, that then extended the
lifetime of the associated objects unpredictably.
|
|
|
|
| |
Because it's really the application domain and not the akonadi domain.
|
|
|
|
|
| |
Otherwise the synchronizer keeps a Storage object alive, while the tests
deletes the db. This causes subsequent writes to fail in the next test.
|
| |
|
|
|
|
|
| |
As queries become reactive this should become less important. We can then just wait until
all results become available. For tests it is in either case useful though.
|
|
|
|
| |
...and a couple of other fixes.
|
|
|
|
| |
until signalling completion.
|
| |
|
|
|
|
| |
The Job/Future in Pipeline::newEntity for some reason crashes with async pipeline processing.
|
| |
|
| |
|
| |
|
| |
|
|
It's a huge hack but starts to show results.
Most urgently we need:
* reliable command results
* the 3 buffers instead of the 1
* A way to implement storage as preprocessor (or a place to impelement it after the preprocessors).
|