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.

Sign up for GitHub

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

Jump to bottom

Document interaction with RawSocket (do not read / write directly) #1186

Closed
dtacalau opened this issue Dec 5, 2019 · 1 comment · Fixed by #1529
Closed

Document interaction with RawSocket (do not read / write directly) #1186

dtacalau opened this issue Dec 5, 2019 · 1 comment · Fixed by #1529
Milestone
V0.8

Comments

@dtacalau
Copy link
Contributor

dtacalau commented Dec 5, 2019

We need to tell users what they are allowed to do when getting the handle of a TcpListener/TcpStream/UdpSocket through as_raw_handle/as_raw_socket on Windows.

Target: v1.0-release
@Thomasdezeeuw
Copy link
Collaborator

The same holds true for Unix, e.g. on Solaris we also need to re-register (see #1152 (comment)).

@dtacalau dtacalau mentioned this issue Dec 6, 2019
Closed
16 tasks
@Thomasdezeeuw Thomasdezeeuw added this to the V0.8 milestone Jan 8, 2021
@Thomasdezeeuw Thomasdezeeuw mentioned this issue Nov 7, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
V0.8
Development

Successfully merging a pull request may close this issue.

Add section about raw fd to portability guidelines Thomasdezeeuw/mio
2 participants
@dtacalau @Thomasdezeeuw