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

std::net::TcpStream::set_nodelay marked as unstable #25201

Closed
icorderi opened this issue May 8, 2015 · 1 comment
Closed

std::net::TcpStream::set_nodelay marked as unstable #25201

icorderi opened this issue May 8, 2015 · 1 comment

Comments

@icorderi
Copy link
Contributor

icorderi commented May 8, 2015

Guys, any particular reason disabling Naggles is still marked as unstable?

@alexcrichton
Copy link
Member

Thanks for the report! The current suite of setting various options for a TcpStream and friends has not received the amount of scrutiny expected from a stable API, and requires thought to consider expansion of the API to more socket options in the future as well as how it plays into other kinds of sockets and such.

We've currently got an RFC issue open about the expansion of the std::net API surface area, and this falls under the category of "More socket options" at the bottom. I hope to write an RFC quite soon for these APIs which will then be slated to hopefully be included as #[stable] in the 1.2 release.

In the meantime, however, the AsRawFd and AsRawSocket traits are #[stable] on Rust master so you can set the options manually (albeit somewhat painfully).

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

2 participants