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

Listening twice to the same port must not silently discard previous listener #292

Open
rixed opened this issue Feb 9, 2017 · 0 comments
Labels

Comments

@rixed
Copy link

rixed commented Feb 9, 2017

This Hashtbl.replace should really throw an error instead:

else Hashtbl.replace t.tcpv4_listeners port callback

For reference, under Unix listening to an already connected socket raises EINVAL (relevant since there is no separate accept operation in Mirage)

@yomimono yomimono added the bug label Nov 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants