Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Socket is not properly ended #50

Open
jbreich opened this issue May 31, 2022 · 0 comments
Open

Socket is not properly ended #50

jbreich opened this issue May 31, 2022 · 0 comments

Comments

@jbreich
Copy link
Contributor

jbreich commented May 31, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant