srtgo
srtgo copied to clipboard
Socket is not properly ended
Hello, I noticed that when an SRT connection is closed from a client streaming data to an SRT server, the server receives a EConnLost error in the read call. I checked with a tcpdump that the SRT client is effectively sending a SHUTDOWN message to be sure it is properly ending the connection.
In this case, I would rather expect an io.EOF error in the read operation to handle it in an idiomatic way. I don't know if it is as simple as EConnLost => io.EOF there are maybe other cases ? Or is there something that I am missing ?
Thanks