summaryrefslogtreecommitdiffstats
path: root/common
Commit message (Collapse)AuthorAge
* Working folder tree queryChristian Mollekopf2015-11-15
|
* DummyResourceTest and QueryTest are passingChristian Mollekopf2015-11-13
| | | | sync has been removed from the query code and is now a separate step
* It's starting to workChristian Mollekopf2015-11-13
|
* A result modelChristian Mollekopf2015-11-10
| | | | | The result model drives the data retrieval and provides the interace for consumers
* CleanupsChristian Mollekopf2015-11-10
|
* Added a folder typeChristian Mollekopf2015-11-09
|
* Fixed warningsChristian Mollekopf2015-11-08
|
* Implemented removeIndexChristian Mollekopf2015-11-05
|
* Fixed shutdown and synchronize commandsChristian Mollekopf2015-10-31
|
* Updated the index on modifications and removals.Christian Mollekopf2015-10-29
| | | | Misses tests.
* Cleanup changereplay, and replay revision 1 as the firstChristian Mollekopf2015-10-28
|
* Correctly execute modifications and removalsChristian Mollekopf2015-10-28
| | | | ... also if there are intermediate revisions.
* Reuse the existing transactionChristian Mollekopf2015-10-28
|
* Made pipeline preprocessing synchronous.Christian Mollekopf2015-10-28
| | | | | | | | | | | | | | | | 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.
* ApplicationDomainType cleanup, define metatypesChristian Mollekopf2015-10-23
|
* We need to return instance identifiers and not resource typesChristian Mollekopf2015-10-23
|
* Made headers installable and install headersChristian Mollekopf2015-10-23
|
* Avoid deadlockChristian Mollekopf2015-10-23
|
* Make it possible to set a new emitter on the listresultmodelChristian Mollekopf2015-10-22
|
* Finished ListResultModel implementation.Christian Mollekopf2015-10-21
|
* CleanupChristian Mollekopf2015-10-21
|
* Avoid hardcoding a made-up resource type for config that doesn't belongChristian Mollekopf2015-10-21
| | | | to a resource
* ClientAPI: Don't require an explicit instance identifierChristian Mollekopf2015-10-21
|
* Moved the ListModelResult to a separate fileChristian Mollekopf2015-10-21
|
* Use a null-resource object to avoid having to check the pointerChristian Mollekopf2015-10-20
| | | | everytime
* Avoid trying to open ResourceAccess twiceChristian Mollekopf2015-10-20
|
* CleanupChristian Mollekopf2015-10-20
|
* Draft of ChangeReplayChristian Mollekopf2015-10-20
|
* More descriptive debug messagesChristian Mollekopf2015-10-20
|
* Color log messagesChristian Mollekopf2015-10-20
|
* CleanupChristian Mollekopf2015-10-20
|
* Test & fix live query removalsChristian Mollekopf2015-10-20
|
* Let clients tell the resource when they no longer require a revision.Christian Mollekopf2015-10-19
|
* CleanupChristian Mollekopf2015-10-15
|
* Moved more entitystorage functionality back to facade.Christian Mollekopf2015-10-15
| | | | | To avoid unnecessary abstraction layers that don't solve a problem, and to allow facades to customize how entities are loaded.
* Dummyclient that can also remove stuff and updates queries automaticallyChristian Mollekopf2015-10-12
|
* Cleanup revisions with a delayChristian Mollekopf2015-10-12
|
* Ignore removed entities while loading the initial result set.Christian Mollekopf2015-10-12
|
* Replay removals.Christian Mollekopf2015-10-11
| | | | | Now we just have to avoid removing the revision too early from the resource.
* Create a new revision for removals as well.Christian Mollekopf2015-10-10
| | | | So we can replay the change.
* Modification and removal in resultsChristian Mollekopf2015-10-10
| | | | | Now we just need to ensure that equality is tested using the ApplicationDomainType::identifier
* A null value means the generator has nothing to generate anymore.Christian Mollekopf2015-10-10
|
* Moved the index to the proper prefixChristian Mollekopf2015-10-10
|
* Only emit the revision update once the batch is committed.Christian Mollekopf2015-10-10
|
* StoreNewRevision functionChristian Mollekopf2015-10-10
|
* CleanupChristian Mollekopf2015-10-10
|
* Always get the latest revision directly from storageChristian Mollekopf2015-10-10
| | | | We can just as well read the latest available revision from storage.
* Change replayChristian Mollekopf2015-10-10
| | | | | So far only includes modifications and additions, removals are not yet stored as separate revisions.
* Revision cleanupChristian Mollekopf2015-09-29
|
* Work with revisions in store + pipelinetestChristian Mollekopf2015-09-24
| | | | Cleanup of revisions, and revision for removed entity is yet missing.
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-26 17:14:16 +0000