Not using a fixed size to read from the RPC socket because one can't know how large an RPC response is going to be. Instead of reading a fixed size and deserialising all msgpack messages inside it, RPC calls have knowledge of how many msgpack responses they expect and they keep reading until satisifed or hitting a timeout.
PEP8-compliant spacing around kwargs.
Adding more tests to get back to 100% code coverage, and PEP8 compliance fixes.
Merge pull request #5 from derpston/fix-rpc-read-size

Not using a fixed size to read from the RPC socket