#tokio #reactor #networking #futures #mio #async #udp-sockets

deprecated tokio-reactor

Event loop that drives Tokio I/O resources

15 releases

0.2.0-alpha.1 Aug 8, 2019
0.1.12 Feb 5, 2020
0.1.11 Nov 27, 2019
0.1.9 Mar 2, 2019
0.1.1 Mar 23, 2018

#299 in #asynchronous

Download history 34415/week @ 2023-02-03 31419/week @ 2023-02-10 34948/week @ 2023-02-17 48826/week @ 2023-02-24 35386/week @ 2023-03-03 35563/week @ 2023-03-10 32534/week @ 2023-03-17 28613/week @ 2023-03-24 29156/week @ 2023-03-31 29457/week @ 2023-04-07 27210/week @ 2023-04-14 28602/week @ 2023-04-21 29390/week @ 2023-04-28 28921/week @ 2023-05-05 32516/week @ 2023-05-12 26734/week @ 2023-05-19

121,941 downloads per month
Used in fewer than 27 crates

MIT license

10K SLoC


Event loop that drives Tokio I/O resources.


This project is licensed under the MIT license.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tokio by you, shall be licensed as MIT, without any additional terms or conditions.


Event loop that drives Tokio I/O resources.

The reactor is the engine that drives asynchronous I/O resources (like TCP and UDP sockets). It is backed by mio and acts as a bridge between mio and futures.

The crate provides:

  • Reactor is the main type of this crate. It performs the event loop logic.

  • Handle provides a reference to a reactor instance.

  • Registration and PollEvented allow third parties to implement I/O resources that are driven by the reactor.

Application authors will not use this crate directly. Instead, they will use the tokio crate. Library authors should only depend on tokio-reactor if they are building a custom I/O resource.

For more details, see reactor module documentation in the Tokio crate.


~32K SLoC