mirror of https://github.com/tokio-rs/tokio.git synced 2026-08-23 00:00:10 +02:00

Files

T

Stjepan Glavina 0f44adf5f6 reactor: use LocalKey::try_with in sharded RW lock (#628 )

@jonhoo reported a panic in the call to `LocalKey::with`, which occurs
when the reactor is dropped in the middle of TLS teardown. This PR
changes the call to `LocalKey::try_with` and handles the case when the
thread-local value has already been destroyed.

2018-09-11 16:48:06 -04:00

examples

Use a scalable RW lock in tokio-reactor (#517 )

2018-08-09 11:23:45 -07:00

src

reactor: use LocalKey::try_with in sharded RW lock (#628 )

2018-09-11 16:48:06 -04:00

Cargo.toml

add experimental async/await support. (#582 )

2018-08-27 12:24:51 -07:00

CHANGELOG.md

add experimental async/await support. (#582 )

2018-08-27 12:24:51 -07:00

LICENSE

Add LICENSE file to all sub crates (#226 )

2018-03-13 13:14:28 -07:00

README.md

Add LICENSE file to all sub crates (#226 )

2018-03-13 13:14:28 -07:00

README.md

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.