Reactive Slick

Here's the ongoing work on Reactive Slick.

/cc @cvogt for review later
Awesome regarding M1. My scalaexchange talk just became available, so it can even show people how to play with it. Ping me when m1 is out and I'll publish a pre-configured usage example.

Regarding master/slave support, no need for M1, but I think it would be a very compelling feature solving a real problem people have that should be easy to handle from the slick side, much harder to handle outside of it. Doing it on top of Slick will not allow dispatching different queries within a larger action to different master/slaves. It requires the necessary architecture and care without any type-safety to make certain to do the right thing. Having a single master is the one performance problem scaling apps can't solve. Anything that helps taking load of master is really helpful to scaling real world apps.