Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
net: document net.Conn operation after deadline is exceeded #17982
The current phrasing on
I'm debugging some non-compliant implementations of
In some of the implementations I'm fixing, once the deadline has been exceeded, the underlying connection is destroyed and it does not matter if the deadline is set to be in the future again; all IO operations henceforth are dead.
Is "refreshable" deadlines an expected behavior of
In general, if Unix and Windows's TCPConn does X, we try to make all implementations (including nacl's and other internal implementations) also do X.
I can't think of anything in std that depends on that behavior, but other things in the broader ecosystem almost certainly do.
I'd err on the side making the internal implementations act like the std TCPConn on linux (and presumably windows).
We could add a CL documenting it if you'd like, but it'd need a test too.
Or we could start with just a test out of curiosity and see what all the current implementations do, even if we don't submit the CL.
Actually, net/http does exactly that.
So we should document this.
Want to send a doc CL, @dsnet?
On the flip-side, what happens when the buffer provided to