Fix Issue #304

This is currently a WIP.  Today I managed to get the major pieces of it in place.  I am not yet passing tests, but the server starts.
As per our discussion, err here occurs when something catastrophic happens in redis. So I would say, we need to create a generic syncmessage that would indicate the fatality of this (something like `ERROR`, `FATAL`) and set the content to something very generic (we don't want to propagate a redis error to the client). As far as how to deal with the error, I would say file another bug for that which would deal with 'recovery' from fatal errors (I don't really know what we could do in this circumstance).