| commit | e1db2bb8d042fb9410f5e4085f487fb5bc8181b6 | [log] [tgz] |
|---|---|---|
| author | Carl Lerche <me@carllerche.com> | Thu Mar 08 20:56:20 2018 -0800 |
| committer | GitHub <noreply@github.com> | Thu Mar 08 20:56:20 2018 -0800 |
| tree | 45fc95439291a5540c74cbddd80fdd2fb2ffb569 | |
| parent | f765c8f59760b8e899c81a649f5d70f9f7c50f6e [diff] |
Update crate to use Tokio reform internally (#303) Tokio reform was released as a separate crate (`tokio`). However, the ecosystem has been split as tokio-core is not compatible with tokio. Libraries (like hyper) that expose tokio-core as part of the public API cannot easily switch to tokio as is. This patch updates tokio-core to use tokio internally. This should help reduce the friction encountered when users attempt to update their code bases to tokio.
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.