#tokio #asynchronous #protocol #transport #tower

tokio-tower

Bridging the protocol gap between Tokio and Tower

10 releases

✓ Uses Rust 2018 edition

new 0.3.5 Feb 21, 2020
0.3.4 Feb 13, 2020
0.3.3 Jan 29, 2020
0.3.0 Dec 20, 2019
0.0.0 Aug 22, 2017

#534 in Network programming

Download history 5/week @ 2019-11-10 15/week @ 2019-11-17 8/week @ 2019-11-24 12/week @ 2019-12-01 27/week @ 2019-12-08 10/week @ 2019-12-15 8/week @ 2019-12-22 1/week @ 2019-12-29 7/week @ 2020-01-05 57/week @ 2020-01-12 52/week @ 2020-01-19 25/week @ 2020-01-26 14/week @ 2020-02-02 52/week @ 2020-02-09 83/week @ 2020-02-16

113 downloads per month
Used in 5 crates (2 directly)

MIT license

74KB
1.5K SLoC

Crates.io Documentation Build Status Dependency status

This crate provides convenient wrappers to make Tokio and Tower work together. In particular, it provides:

  • server bindings wrappers that combine a tower::Service with a transport that implements Sink<SinkItem = Request> and Stream<Item = Response>.
  • client wrappers that implement tower::Service for transports that implement Sink<SinkItem = Request> and Stream<Item = Response>.

Take a look at the crate documentation for details.

Dependencies

~4MB
~69K SLoC