tokio-reactor

Event loop that drives Tokio I/O resources.

5 releases

0.1.3 Aug 7, 2018
0.1.2 Jun 13, 2018
0.1.1 Mar 23, 2018
0.1.0 Mar 9, 2018
0.0.0 Feb 1, 2018

#1 in Asynchronous

Download history 13243/week @ 2018-05-16 16022/week @ 2018-05-23 15375/week @ 2018-05-30 17122/week @ 2018-06-06 16073/week @ 2018-06-13 20543/week @ 2018-06-20 18437/week @ 2018-06-27 16002/week @ 2018-07-04 18240/week @ 2018-07-11 17926/week @ 2018-07-18 17088/week @ 2018-07-25 16709/week @ 2018-08-01 19657/week @ 2018-08-08

74,145 downloads per month

tokio-reactor

Event loop that drives Tokio I/O resources.

Documentation

Overview

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.

License

This project is licensed under the MIT license.

Contribution

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.

MIT license

Dependencies

Reverse deps