In golang what error will TCPConn.Write/Read return?

Question

In golang, how would you handle error return by TCPConn.Read/Write? this document did not say anything about read/write errors.

Answer 1

Read and Write on a TCPConn could return most of errors that your combination of OS, hardware and drivers could return, along with some net package errors, and io.EOF when applicable. So it's really up to you to know what errors to look for, and how to handle them. Every layer of network API, even the berkeley socket api, is a leaky abstraction, and you can't make full use of it without understanding how the actual sockets and network protocols work.

Usually you only need be concerned with io.EOF , which is returned by Conn.Read when the connection is closed. On a TCP socket, this is the equivalent of recv returning 0 bytes on a blocking connection.

Any other errors that you could handle are usually wrapped in a net.Error , which provides the Temporary() and Timeout() methods. Often the real error type is a *net.OpError , which can provide even more information about when the error occurred, as well as encapsulate the actual error returned by the operation.