tokio-timer-plus 0.1.3

Timer facilities for Tokio
Documentation
  • Coverage
  • 100%
    23 out of 23 items documented1 out of 11 items with examples
  • Size
  • Source code size: 69.67 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 5.16 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 13s Average build duration of successful builds.
  • all releases: 13s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • tokio-rs/tokio-timer
    85 21 13
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • sorpaas

tokio-timer

Timer facilities for Tokio

Build Status Crates.io

Documentation | Gitter

Usage

First, add this to your Cargo.toml:

[dependencies]
tokio-timer = "0.1"

Next, add this to your crate:

extern crate tokio_timer;

What is tokio-timer?

This crate provides timer facilities for usage with Tokio. Currently, the only timer implementation is a hashed timing wheel, but will provide a binary heap based timer at some point.

A timer provides the ability to set a timeout, represented as a future. When the timeout is reached, the future completes. This can be implemented very efficiently and avoiding runtime allocations.

Hashed Timing Wheel

Inspired by the paper by Varghese and Lauck, the hashed timing wheel is a great choice for the usage pattern commonly found when writing network applications.

License

tokio-timer 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.

The MPMC queue implementation is inspired from 1024cores, see LICENSE-MPMC for details.