Client sending packets faster than Tokio-based TCP server can read

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • whirl

    ✨ The Open-Source WorldServer (by Whirlsplash)

    However, I still had the exact same issue, down to the details, some packets were just not received. Here is what the file looked like at that state, very different but same issue. I checked Wireshark and the client does seem to be sending the FULL packets but the server literally just never replies, that’s what leads me to speculate the issue derives from some blocking action that is performed.

  • tokio-serde-json

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  • mini-redis

    Incomplete Redis client and server implementation using Tokio - for learning purposes only

    Serializing messages is a large part of mini-redis, and its source is pretty easy to read. You can also try to implement it using tokio_util::codec, which is a library that helps with implementing this kind of stuff. It has some decent examples on the link as well.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts