tag | 0aa043c05fce0a561251d34da6c5a97246d69702 | |
---|---|---|
tagger | Alex Crichton <alex@alexcrichton.com> | Fri Jan 06 11:39:44 2017 -0800 |
object | 76c3e162b702c5a654fd22f1597266fcd81d188b |
Version 0.1.3 * Add a doc url to the crate * Remove an allocation in `TcpStream::connect` * Touch up a few docs here and there
commit | 76c3e162b702c5a654fd22f1597266fcd81d188b | [log] [tgz] |
---|---|---|
author | Alex Crichton <alex@alexcrichton.com> | Fri Jan 06 11:39:38 2017 -0800 |
committer | Alex Crichton <alex@alexcrichton.com> | Fri Jan 06 11:39:38 2017 -0800 |
tree | db239ecbefb1624a73857107af4d76b3e8bca48b | |
parent | 64c360c30ebfadc8b5333206482a78d4f62975f4 [diff] |
Bump to 0.1.3
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.