Reactive Slick

Here's the ongoing work on Reactive Slick.

/cc @cvogt for review later
You mean for using Future.apply? No, since it's not just overhead. Using Future.apply is conceptionally wrong. IMHO it does not make sense for scheduleSynchronousStreaming to return a Future which is immediately discarded just in order to run some code on an ExecutionContext.