commit | 64c360c30ebfadc8b5333206482a78d4f62975f4 | [log] [tgz] |
---|---|---|
author | Alex Crichton <alex@alexcrichton.com> | Fri Jan 06 11:32:05 2017 -0800 |
committer | Alex Crichton <alex@alexcrichton.com> | Fri Jan 06 11:37:46 2017 -0800 |
tree | 5214a3c757c5dd7bd78a0437ed979d43b0bd2300 | |
parent | 2499dd35a2517690fbf7ec8e14e5522c1c9ae50f [diff] |
Touch up `TcpStream::connect` and revert breaking change
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;
There are a few small examples showing off how to use this library:
This crate is a connection between futures
, a zero-cost implementation of futures in Rust, and mio
, a crate for zero-cost asynchronous I/O. The types and structures implemented in tokio-core
implement Future
and Stream
traits as appropriate. For example, connecting a TCP stream returns a Future
resolving to a TCP stream, and a TCP listener implements a stream of TCP streams (accepted connections).
This crate also provides facilities such as:
Executor
implementation for a futures' Task
The intention of tokio-core
is to provide a concrete implementation for crates built on top of asynchronous I/O. For example you can easily turn a TCP stream into a TLS/SSL stream with the tokio-tls
crate or use the combinators to compose working with data on sockets.
Check out the documentation for more information, and more coming here soon!
tokio-core
is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with portions covered by various BSD-like licenses.
See LICENSE-APACHE, and LICENSE-MIT for details.