sink - A data access layer handling synchronization, caching and indexing

	Commit message (Collapse)	Author	Age
*	Only query for new revisions.	Christian Mollekopf	2015-07-27
\| \| \| \| \|	Instead of clearing the result everytime we only query for the stuff that has changed.
*	Removed hardcoded instance identifier	Christian Mollekopf	2015-07-27
\|
*	More trace messages	Christian Mollekopf	2015-07-23
\|
*	Modify/Delete actions	Christian Mollekopf	2015-07-19
\|
*	Don't require a smartpointer where not necessary	Christian Mollekopf	2015-07-15
\|
*	Removed unnecessary template parameter	Christian Mollekopf	2015-07-14
\|
*	Generalized facade code.	Christian Mollekopf	2015-07-02
\| \| \| \|	A default implementation is now nothing but an empty shell.
*	Use template type parameter	Christian Mollekopf	2015-06-01
\|
*	KAsync has moved to it's own kasync.git repository	Dan Vrátil	2015-05-18
\|
*	Adapt to KAsync namespace change	Dan Vrátil	2015-05-15
\|
*	Ensure the facade is open when listening to revision changes.	Christian Mollekopf	2015-05-01
\|
*	Moved the non-generic code back to dummyresource.	Christian Mollekopf	2015-04-27
\| \| \| \|	The dummy resource could now implement incremental queries.
*	Fixed lifetime management of resultSet.	Christian Mollekopf	2015-04-27
\| \| \| \| \|	The resultSet remains valid for the duration of the thread. We keep the thread running until the ResultEmitter is deleted.
*	Moved complete writing part to GenericFacade	Christian Mollekopf	2015-04-19
\|
*	Moved generic part of load to GenericFacade	Christian Mollekopf	2015-04-18
\|
*	Use a queryrunner to execute queries.	Christian Mollekopf	2015-04-15
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Started a facade base implementation.	Christian Mollekopf	2015-04-09