Expand description
Event loop that drives Tokio I/O resources.
Note: This crate is deprecated in tokio 0.2.x and has been moved and refactored into various places in the
tokio::runtime
andtokio::io
modules of thetokio
crate. The Reactor has also been renamed the “I/O Driver”.
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
andPollEvented
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.
Structs§
- Handle to the reactor running on a background thread.
- Ensure that the default reactor is removed from the thread-local context when leaving the scope. This handles cases that involve panicking.
- A reference to a reactor.
- Associates an I/O resource that implements the
std::io::Read
and/orstd::io::Write
traits with the reactor that drives it. - The core reactor, or event loop.
- Associates an I/O resource with the reactor instance that drives it.
- Error returned from
Handle::set_fallback
. - Future that resolves when the reactor thread has shutdown.
- Return value from the
turn
method onReactor
.
Functions§
- Sets
handle
as the default reactor, returning a guard that unsets it when dropped. - Set the default reactor for the duration of the closure