The network-utils crate is very useful for developers, but currently it forces the implementation to spin up 2 async tasks and rely on async channels to communicate with client. This requires 2 sequential async awaits for every Tcp read and write which is not very performant. Instead, the crate should return the a type similar to a typical tcp stream type (one that implements the AsyncRead and AsyncWrite). In addition, the type returned should implement into_split() (see https://docs.rs/tokio/latest/tokio/net/struct.TcpStream.html#method.into_split), so that the user has the option to separate the reader and writer into different tasks if warranted.