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

Docs & code claim that Network.framework treats SO_REUSEADDR & SO_REUSEPORT as the same, don't think that's true #81

Open
weissi opened this issue Apr 22, 2020 · 0 comments

Comments

@weissi
Copy link
Member

weissi commented Apr 22, 2020

I don't think this comment is right.

// Network.framework munges REUSEADDR and REUSEPORT together, so we turn this on if we need
// either.

That is the equivalent of SO_REUSEADDR. From what I can tell, it's not possible to do SO_REUSEPORT from Network.framework, at least I haven't managed to bind two processes to the same port.

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