TcpClient.GetStream().Read() vs. TcpClient.Client.Receive()

Question

.NET allows two very similar ways to \"read\" from the network (assuming TCP connection):

1. TcpClient.GetStream().Read() 
2. TcpClient.Client.Receive()


        

Answer 1

There is, in fact, a pretty clear benefit of using the first option (TcpStream and not Socket). The benefit is that stream API is more flexible when different underlying implementations are needed at for the same program.

For example, a code which sometimes may use SSL and sometimes may not use it, can switch between SslStream and TcpStream with no changes to the calling code. This is something which is much harder to accomplish using only plain Socket API.

Answer 2

Nothing, really. It's just that sometimes it's more convenient to use a Stream.

Answer 3

To me, a successful Socket.Receive operation with zero bytes received tells you that connection is closed.