commit | 389bc3bd4f49ef1783aa2f521cb87b7ace34a1c3 | [log] [tgz] |
---|---|---|
author | Carl Lerche <me@carllerche.com> | Sun Mar 11 14:31:23 2018 -0700 |
committer | GitHub <noreply@github.com> | Sun Mar 11 14:31:23 2018 -0700 |
tree | eec48874e8704d33b20c31721cff955d7dfd681a | |
parent | 4b88d0280ffae71a0b324d0984028ad4fbe5d1ff [diff] |
Drain remote queue before blocking. (#312) Unless this is done before blocking, sending a command over the remote channel will not be able to wake up a blocked reactor. Fixes #311
This crate is scheduled for deprecation in favor of tokio.
tokio-core
is still actively maintained, but only bug fixes will be applied. All new feature development is happening in tokio.
Core I/O and event loop abstraction for asynchronous I/O in Rust built on futures
and mio
.
First, add this to your Cargo.toml
:
[dependencies] tokio-core = "0.1"
Next, add this to your crate:
extern crate tokio_core;
You can find extensive documentation and examples about how to use this crate online at https://tokio.rs as well as the examples
folder in this repository. The API documentation is also a great place to get started for the nitty-gritty.
This project is licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in tokio-core by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.