| commit | 85a90f483d53abc7609a8467fde6176a494113a9 | [log] [tgz] |
|---|---|---|
| author | Carl Lerche <me@carllerche.com> | Fri May 24 14:42:01 2019 -0700 |
| committer | Thomas de Zeeuw <thomasdezeeuw@gmail.com> | Mon May 27 18:35:08 2019 +0000 |
| tree | a86ef7c1c1b4adc3f61c1d41e56de17b8c660cfd | |
| parent | 64f2cd45152bdf8857a3c1f857fb177202eede2a [diff] |
Do not trigger HUP events on kqueue Previously, mio would attempt to provide HUP events for kqueue platforms that mimic the epoll behavior. However, it is not possible to do this reliably. The assumption was that when an EVFILT_WRITE event is raised with EOF set, this had to be the final event for a TCP socket due to how the TCP protocol works. As it turns out, user actions as well as external events can trigger kqueue events. When the user calls `shutdown(SHUT_WR)`, this results in an EVFILT_WRITE event with EOF set. Converting this to HUP at this point is incorrect as data may still be received
Mio is a lightweight I/O library for Rust with a focus on adding as little overhead as possible over the OS abstractions.
API documentation
This is a low level library, if you are looking for something easier to get started with, see Tokio.
To use mio, first add this to your Cargo.toml:
[dependencies] mio = "0.6"
Then, add this to your crate root:
extern crate mio;
The following are specifically omitted from Mio and are left to the user or higher-level libraries.
Currently supported platforms:
There are potentially others. If you find that Mio works on another platform, submit a PR to update the list!
A group of Mio users hang out in the #mio channel on the Mozilla IRC server (irc.mozilla.org). This can be a good place to go for questions.
Interested in getting involved? We would love to help you! For simple bug fixes, just submit a PR with the fix and we can discuss the fix directly in the PR. If the fix is more complex, start with an issue.
If you want to propose an API change, create an issue to start a discussion with the community. Also, feel free to talk with us in the IRC channel.
Finally, be kind. We support the Rust Code of Conduct.