#io #async #non-blocking #futures

tokio

An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications

10 releases

0.1.8 Aug 24, 2018
0.1.7 Jun 7, 2018
0.1.6 May 2, 2018
0.1.5 Mar 30, 2018
0.0.0 Jul 1, 2016

#7 in Asynchronous

Download history 19030/week @ 2018-09-05 21941/week @ 2018-09-12 25272/week @ 2018-09-19 21814/week @ 2018-09-26 29027/week @ 2018-10-03 26849/week @ 2018-10-10 27961/week @ 2018-10-17 26129/week @ 2018-10-24 30114/week @ 2018-10-31 29612/week @ 2018-11-07 30012/week @ 2018-11-14 28983/week @ 2018-11-21 30057/week @ 2018-11-28

76,434 downloads per month
Used in 1,483 crates (296 directly)

MIT license

796KB
12K SLoC

Tokio

A runtime for writing reliable, asynchronous, and slim applications with the Rust programming language. It is:

  • Fast: Tokio's zero-cost abstractions give you bare-metal performance.

  • Reliable: Tokio leverages Rust's ownership, type system, and concurrency model to reduce bugs and ensure thread safety.

  • Scalable: Tokio has a minimal footprint, and handles backpressure and cancellation naturally.

Crates.io MIT licensed Travis Build Status Appveyor Build Status Gitter chat

Website | Guides | API Docs | Chat

The API docs for the master branch are published here.

Overview

Tokio is an event-driven, non-blocking I/O platform for writing asynchronous applications with the Rust programming language. At a high level, it provides a few major components:

  • A multithreaded, work-stealing based task scheduler.
  • A reactor backed by the operating system's event queue (epoll, kqueue, IOCP, etc...).
  • Asynchronous TCP and UDP sockets.

These components provide the runtime components necessary for building an asynchronous application.

Example

A basic TCP echo server with Tokio:

extern crate tokio;

use tokio::prelude::*;
use tokio::io::copy;
use tokio::net::TcpListener;

fn main() {
    // Bind the server's socket.
    let addr = "127.0.0.1:12345".parse().unwrap();
    let listener = TcpListener::bind(&addr)
        .expect("unable to bind TCP listener");

    // Pull out a stream of sockets for incoming connections
    let server = listener.incoming()
        .map_err(|e| eprintln!("accept failed = {:?}", e))
        .for_each(|sock| {
            // Split up the reading and writing parts of the
            // socket.
            let (reader, writer) = sock.split();

            // A future that echos the data and returns how
            // many bytes were copied...
            let bytes_copied = copy(reader, writer);

            // ... after which we'll print what happened.
            let handle_conn = bytes_copied.map(|amt| {
                println!("wrote {:?} bytes", amt)
            }).map_err(|err| {
                eprintln!("IO error {:?}", err)
            });

            // Spawn the future as a concurrent task.
            tokio::spawn(handle_conn)
        });

    // Start the Tokio runtime
    tokio::run(server);
}

More examples can be found here.

Getting Help

First, see if the answer to your question can be found in the [Guides] or the [API documentation]. If the answer is not there, there is an active community in the Tokio Gitter channel. We would be happy to try to answer your question. Last, if that doesn't work, try opening an issue with the question.

Contributing

:balloon: Thanks for your help improving the project! We are so happy to have you! We have a contributing guide to help you get involved in the Tokio project.

Project layout

The tokio crate, found at the root, is primarily intended for use by application developers. Library authors should depend on the sub crates, which have greater guarantees of stability.

The crates included as part of Tokio are:

  • tokio-async-await: Experimental async / await support.

  • tokio-codec: Utilities for encoding and decoding protocol frames.

  • tokio-current-thread: Schedule the execution of futures on the current thread.

  • tokio-executor: Task execution related traits and utilities.

  • tokio-fs: Filesystem (and standard in / out) APIs.

  • tokio-io: Asynchronous I/O related traits and utilities.

  • tokio-reactor: Event loop that drives I/O resources (like TCP and UDP sockets).

  • tokio-tcp: TCP bindings for use with tokio-io and tokio-reactor.

  • tokio-threadpool: Schedules the execution of futures across a pool of threads.

  • tokio-timer: Time related APIs.

  • tokio-udp: UDP bindings for use with tokio-io and tokio-reactor.

  • tokio-uds: Unix Domain Socket bindings for use with tokio-io and tokio-reactor.

Supported Rust Versions

Tokio is built against the latest stable, nightly, and beta Rust releases. The minimum version supported is the stable release from three months before the current stable release version. For example, if the latest stable Rust is 1.29, the minimum version supported is 1.26. The current Tokio version is not guaranteed to build on Rust versions earlier than the minimum supported version.

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.

Dependencies

~3.5MB
~52K SLoC