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

net_tcp doesn't use SO_REUSEADDR #3597

Closed
jesse99 opened this issue Sep 26, 2012 · 6 comments
Closed

net_tcp doesn't use SO_REUSEADDR #3597

jesse99 opened this issue Sep 26, 2012 · 6 comments

Comments

@jesse99
Copy link
Contributor

jesse99 commented Sep 26, 2012

which is really annoying.

@catamorphism
Copy link
Contributor

Nominating for milestone 3, feature-complete

@bblum
Copy link
Contributor

bblum commented Jun 10, 2013

libextra::timer and libextra::net_tcp are deprecated pending #6435. Is this still functionality that will be needed in the new implementation?

@metajack
Copy link
Contributor

Yes. SO_REUSEADDR is very commonly used.

@pnkfelix
Copy link
Member

sounds critical for implementing server. accepted for feature complete

(did I mean to say "Servo" above? Not my area of expertise, clearly.)

@anasazi
Copy link
Contributor

anasazi commented Sep 18, 2013

I don't think this is relevant in the new runtime's non-blocking I/O (libuv takes care of this stuff internally).
Unless we're going to write a native I/O interface, then I think we can close this.

@alexcrichton
Copy link
Member

Closing due to the libextra modules having been jettisoned and libuv handling this much differently.

RalfJung pushed a commit to RalfJung/rust that referenced this issue May 11, 2024
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

7 participants