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

	Commit message (Collapse)	Author	Age
...
*	Async: make the processing truly asynchronous	Dan Vrátil	2014-12-14
\| \| \| \| \| \|	Now calling exec() starts the first job and returns a pending Future immediately. Caller can then use Async::FutureWatcher to wait for the future to become finished, i.e. for all jobs to finish execution.
*	Async: make it build again	Dan Vrátil	2014-12-12
\|
*	Drop a temporary file	Dan Vrátil	2014-12-12
\|
*	Async: add some simple documentation	Dan Vrátil	2014-12-12
\|
*	Async: move some more code out-of-line	Dan Vrátil	2014-12-12
\|
*	Async: move some common code from executors to shared base class	Dan Vrátil	2014-12-12
\|
*	Async: add Reduce task	Dan Vrátil	2014-12-12
\|
*	Async: move the actual task exection into Executor implementation	Dan Vrátil	2014-12-11
\| \| \| \| \| \| \|	As of now, Job is only front interface to a chain of Executor subclasses. Each Executor subclass specializes for given type of execution (then, each, reduce, ...), and the chain is then executed recursively, as we did with the original Job implementation.
*	Async: change syntax of callables	Dan Vrátil	2014-12-11
\| \| \| \| \| \|	We now pass our own Async::Future to each task, instead of expecting tasks to return their future. This allows us to re-use the same Future for repeated invocations, like in the Each task.
*	Async: move some definitions out-of-line	Dan Vrátil	2014-12-11
\|
*	Async: simplify the template magic around In... being empty or void	Dan Vrátil	2014-12-11
\|
*	Prototype of Async library	Dan Vrátil	2014-12-11