Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | ResourceAccess: copy the buffer before capturing it in the lambda. | Christian Mollekopf | 2015-04-02 |
| | | | | | | | | | | | It's lifetime is limited to the end of the function, so we have to copy it before. I switched to QByteArray because it simplifies the code and shouldn't really cost anything, additionally the implicit sharing makes copies cheap. This patch incurs the cost of always copying the buffer instead of writing straight to the socket, but we probably anyways want to keep a copy around, and if it would indeed be a performance issues (I doubt it), we could still optimize that copy away. | ||
* | async simplifications | Christian Mollekopf | 2015-04-02 |
| | |||
* | Unbreak the clientapi. | Christian Mollekopf | 2015-04-02 |
| | | | | We indeed have to keep the facade alive, otherwise this starts crashing. | ||
* | Cleanup and debug messages. | Christian Mollekopf | 2015-04-02 |
| | |||
* | Storage: API cleanup/use QByteArray instead of std::string | Christian Mollekopf | 2015-03-31 |
| | |||
* | Don't try to restart the resource on every disconnect. | Christian Mollekopf | 2015-03-31 |
| | | | | | There's a chance that the resource actually wanted to shut-down. Instead ResourceAccess should only reopen the connection if it still has work to do. | ||
* | Forgot to compile the notification schema | Christian Mollekopf | 2015-03-31 |
| | |||
* | Minor cleanup, less warnings. | Christian Mollekopf | 2015-03-31 |
| | |||
* | Shutdown notification to achieve a clean shutdown. | Christian Mollekopf | 2015-03-31 |
| | | | | | | | Otherwise the client always restarts the resource because of the lost connection. We currently require this in tests to be able to delete the db, but eventually we likely want a "disable akonadi" function that shuts resources down, and keeps clients from restarting them (e.g. via configuration). | ||
* | Resource crashhandler and logging facilities. | Christian Mollekopf | 2015-03-31 |
| | |||
* | Async: allow appending Jobs to already running or finished Jobs | Dan Vrátil | 2015-02-21 |
| | | | | | | | | | When user gets a Job (from a method call for instance), which is already running or might have even finished already, they can still append a new Job to the chain and re-execute it. The Job will internally chain up to the last finished Job, use it's result and continue from the next Job in the chain. If a Job in the chain is still running, it will wait for it to finish and pass the result to the next Job in the chain. | ||
* | CMake: fix Qt5 lookup, use KDE_INSTALL_TARGETS_DEFAULT_ARGS | Dan Vrátil | 2015-02-21 |
| | |||
* | Async: allow appending existing Job objects to the Job chain | Dan Vrátil | 2015-02-20 |
| | | | | | | | | | | | | Now it's possible to do something like Job<int, int> job = createSomeJob(); auto main = Async::start<int>(....).then(job); Previously the 'job' would have to be wrapped in a ThenTask-like lambda (which is what we still do internally), but with this new syntax it's possible to append another job chain to existing chain easilly. This syntax is available for all task types. | ||
* | catch unqlite impl up to current Storage API | Aaron Seigo | 2015-02-09 |
| | |||
* | void const -> const void | Aaron Seigo | 2015-02-09 |
| | | | | | equivalent syntax, but follows the standard idiom we use throughout the code .. const char *, not char const * (e.g.) | ||
* | Added JOBAPI todo's. | Christian Mollekopf | 2015-02-02 |
| | | | | Work for dvratil. | ||
* | clenup | Christian Mollekopf | 2015-01-30 |
| | |||
* | Shutdown command for synchronizers, used by the dummyresourcetest. | Christian Mollekopf | 2015-01-30 |
| | | | | | Otherwise the synchronizer keeps a Storage object alive, while the tests deletes the db. This causes subsequent writes to fail in the next test. | ||
* | Open the database readonly in readonly mode. | Christian Mollekopf | 2015-01-30 |
| | |||
* | introduce a set of isInternalKey functions to hide this impl detail | Aaron Seigo | 2015-01-27 |
| | |||
* | can not delete this as it is an opaque data structure | Aaron Seigo | 2015-01-27 |
| | | | | instead, use the lmdb api | ||
* | fix build | Aaron Seigo | 2015-01-27 |
| | |||
* | Don't enlessly block in the eventloop. | Christian Mollekopf | 2015-01-27 |
| | | | | | The job currently finishes synchronously. If we just use the eventloop in waitForFinished that's automatically handled for us. | ||
* | debug output | Christian Mollekopf | 2015-01-25 |
| | |||
* | Propagate errors for commands. | Christian Mollekopf | 2015-01-25 |
| | |||
* | Call callbacks after the resource crashed. | Christian Mollekopf | 2015-01-25 |
| | |||
* | debug output, fixed dummyresourcetest | Christian Mollekopf | 2015-01-25 |
| | |||
* | A way to ensure all messages have been processed. | Christian Mollekopf | 2015-01-25 |
| | | | | | 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. | ||
* | Uid index + query using that index. | Christian Mollekopf | 2015-01-24 |
| | | | | ...and a couple of other fixes. | ||
* | An index implementation. | Christian Mollekopf | 2015-01-21 |
| | |||
* | Create buffer with values from domain object | Christian Mollekopf | 2015-01-21 |
| | |||
* | Storage: support for duplicates. | Christian Mollekopf | 2015-01-20 |
| | |||
* | Fixed sync, detect errors during sync, wait until sync items are processed ↵ | Christian Mollekopf | 2015-01-19 |
| | | | | until signalling completion. | ||
* | debug output | Christian Mollekopf | 2015-01-19 |
| | |||
* | Fixed pipeline. | Christian Mollekopf | 2015-01-19 |
| | | | | Steps are now finally processed as they should be and a job tracks the processing progress. | ||
* | Use jobs in queries, sync works again. | Christian Mollekopf | 2015-01-18 |
| | |||
* | Use jobs to track progress of write commands. | Christian Mollekopf | 2015-01-18 |
| | |||
* | Fixed storage removal. | Christian Mollekopf | 2015-01-16 |
| | | | | We have to remove any open environments as well. | ||
* | Async message queue processing. | Christian Mollekopf | 2015-01-15 |
| | | | | The Job/Future in Pipeline::newEntity for some reason crashes with async pipeline processing. | ||
* | Fixed messageqeue and storage. Empty scan is not an error. | Christian Mollekopf | 2015-01-15 |
| | |||
* | Writing from facade. | Christian Mollekopf | 2015-01-15 |
| | |||
* | Fixed messagequeue | Christian Mollekopf | 2015-01-15 |
| | |||
* | Finally working multithreaded reads from lmdb? | Christian Mollekopf | 2015-01-11 |
| | |||
* | Error handling for remove. | Christian Mollekopf | 2015-01-11 |
| | |||
* | A messagequeue. | Christian Mollekopf | 2015-01-11 |
| | |||
* | Remove from storage call. | Christian Mollekopf | 2015-01-11 |
| | |||
* | Fixed turning read transactions into write transactions. | Christian Mollekopf | 2015-01-11 |
| | |||
* | Made the domain adaptor actually work. We can read stuff now. | Christian Mollekopf | 2015-01-07 |
| | |||
* | Turned synchronizeResource command into a job. | Christian Mollekopf | 2015-01-06 |
| | |||
* | Pass entity to preprocessor. | Christian Mollekopf | 2015-01-03 |
| |