CODEWITHSUNDEEP
c#.netsockets
Borka
Borka

Reputation: 2209

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

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

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

By looking at NetworkStream source code - it seems that it's an extra wrapper over the underlying socket, which eventually calls Socket methods.

Question: what's the benefit of using "indirect" NetworkStream variation (#1), instead of using direct wrapper provided by Socket implementation?

Thank you, Boris.

Upvotes: 6

Views: 8483

Answers (3)

ashepetko
ashepetko

Reputation: 1

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

Upvotes: -1

Borka
Borka

Reputation: 2209

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.

Upvotes: 13

Gonzalo
Gonzalo

Reputation: 21175

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

Upvotes: 1

Related Questions