---
title: "Tokio"
description: "1 posts about Tokio, summarised, each linking to the original."
---

# Tokio
> 1 posts about Tokio, summarised, each linking to the original.

## Articles

### [The Tokio Upgrade from 0.2 to 1.x](https://yomu.fyi/post/the-tokio-upgrade-from-0-2-to-1-x.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: Feb 12, 2021
- Type: Tutorial

Fly.io’s Rust-based load balancer handles almost all of its traffic and stands on Tokio and Hyper, motivating an upgrade from Tokio 0.2 to 1.0. The team waited to upgrade until related crates including hyper, reqwest, async-compression, tokio-io-timeout, tokio-tungstenite, and sentry were ready; after a few weeks, most of the ecosystem had upgraded. The migration foregoes Tokio’s Stream implementations pending stabilization in the standard library, relaxes mutable-access requirements, changes AsyncRead and AsyncWrite polling to return Result<()>, and requires more explicit pinning for !Unpin futures. Because runtime::Handle lacked block\_on, the team worked around the restriction with Arc; standard TcpListener values also required set\_nonblocking(true) before TcpListener::from\_std. Other changes included renamed APIs and revised Hyper WebSocket upgrades, and the author says the major upgrade was not hard.