Implementing the streaming response back to client

Instead of using a redis client wrapped with the raw protocol, we now just use a simple tcp connection for handling request/response.
There is one extra status check redis connection that is used to track the redis status and issue info/slave of etc commands

This means
 * that Large responses are handled correctly
 * There is no conversion from one socket to another. Thus a performance boost esp for large responses.
 * Large number of events hooked up have been removed.

 There is still some cruft remaining with the read part of the protocol. Where a stream would help as well.
Unpiping the response for ultimate magic