Parse Transfer Encodings that we don't handle

We should not throw away information here, as downstream users
may want to handle alternative encodings.
Abstract out NetworkStream

This introduces a new Trait, NetworkStream, which abstracts over
the functionality provided by TcpStream so that it can be easily
mocked and extended in testing and hyper can be used for
other connection sources.
Merge pull request #30 from reem/dont-lose-transfer-encoding

Parse Transfer Encodings that we don't handle
Use trait objects and dynamic dispatch to abstract over NetworkStream

Server and client benchmarks show that this makes very little difference
in performance and using dynamic dispatch here is significantly more ergonomic.

This also bounds NetworkStream with Send to prevent incorrect implementations.

Allows the implementation of mock streams for testing and flexibility.

Fixes #5
Deny missing documentation and all warnings for cleaner builds.
Use dynamic dispatch for client Request and Response through Box<NetworkStream>

Also adds a convenience `abstract` method to NetworkStream for creating
Box<NetworkStream + Send> from a NetworkStream.
Update benchmarks and introduce more default type params for remaining generics

The client benchmarks did not have to be changed at all for this whole
refactor, and the server benchmark only had to specify a single type parameter,
and only because it writes out the type of Listener, which is not normal
usage.
Merge pull request #29 from reem/network-stream

Abstract over NetworkStream using dynamic dispatch