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

	Commit message (Collapse)	Author	Age
*	Don't create a transaction for every revision that we don't replay.	Christian Mollekopf	2016-09-15
\| \| \| \| \|	This had a significant performance impact when i.e. syncing a folder with 10k messages.
*	Prepare for making the resource status available	Christian Mollekopf	2016-07-05
\|
*	Non blocking change-replay	Christian Mollekopf	2016-06-02
\|
*	Open a valid database also in the NullChangeReplay and skip internal keys	Christian Mollekopf	2016-05-31
\|
*	Refactored the generic resource to use separate classes for	Christian Mollekopf	2016-05-28
	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.