Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | 30-Mar-2022 | - | ||||
src/ | H | 30-Mar-2022 | - | 2,525 | 1,365 | |
.cargo-checksum.json | H A D | 03-May-2022 | 89 | 1 | 1 | |
CHANGELOG.md | H A D | 30-Mar-2022 | 357 | 19 | 11 | |
Cargo.toml | H A D | 30-Mar-2022 | 1.1 KiB | 41 | 34 | |
LICENSE | H A D | 30-Mar-2022 | 1 KiB | 26 | 22 | |
README.md | H A D | 30-Mar-2022 | 1.5 KiB | 43 | 28 |
README.md
1# tokio-reactor 2 3Event loop that drives Tokio I/O resources. 4 5[Documentation](https://tokio-rs.github.io/tokio/tokio_reactor/) 6 7## Overview 8 9The reactor is the engine that drives asynchronous I/O resources (like TCP and 10UDP sockets). It is backed by [`mio`] and acts as a bridge between [`mio`] and 11[`futures`]. 12 13The crate provides: 14 15* [`Reactor`] is the main type of this crate. It performs the event loop logic. 16 17* [`Handle`] provides a reference to a reactor instance. 18 19* [`Registration`] and [`PollEvented`] allow third parties to implement I/O 20 resources that are driven by the reactor. 21 22Application authors will not use this crate directly. Instead, they will use the 23[`tokio`] crate. Library authors should only depend on `tokio-reactor` if they 24are building a custom I/O resource. 25 26[`mio`]: http://github.com/carllerche/mio 27[`futures`]: http://github.com/rust-lang-nursery/futures-rs 28[`Reactor`]: https://tokio-rs.github.io/tokio/tokio_reactor/struct.Reactor.html 29[`Handle`]: https://tokio-rs.github.io/tokio/tokio_reactor/struct.Handle.html 30[`Registration`]: https://tokio-rs.github.io/tokio/tokio_reactor/struct.Registration.html 31[`PollEvented`]: https://tokio-rs.github.io/tokio/tokio_reactor/struct.PollEvented.html 32[`tokio`]: ../ 33 34## License 35 36This project is licensed under the [MIT license](LICENSE). 37 38### Contribution 39 40Unless you explicitly state otherwise, any contribution intentionally submitted 41for inclusion in Tokio by you, shall be licensed as MIT, without any additional 42terms or conditions. 43