Handling of Errors in async ops/ TCPClient
TylerADavis opened this issue · comments
Come up with a way for the server to notify the client of errors, and for the futures to convey that error back to the user.
Resolved in #67
Async ops present a new form of error. Namely, it is possible that a client sends multiple read requests to the server, and one of them fails. This will then result in the client halting when it is notified. However, the server will then try to send a second message to the client for another read request, resulting in the server attempting to write to a broken connection and also terminating.
Rather than terminating when it encounters an error writing to the client, the server should log the error and continue.
I believe this can be closed as the async ops branch was merged