tungstenite-rs

If you run your tracker on Linux and an info hash whitelist approach would work for your use case, it might be worthwhile to have a look at aquatic_ws [0]. It relies on tungstenite [1] for websockets and achieves around 20x the throughput of the reference implementation when running with four threads. I don’t know of anybody who runs it in production, but its sister implementation (BitTorrent over UDP) handles 80k responses per second with lower load averages than opentorrent. [0] https://github.com/greatest-ape/aquatic [1]: https://github.com/snapview/tungstenite-rs (I am the developer of aquatic)

I get the arguments why lowercasing is better, and it's certainly more beautiful than making everything caps, but the transition from the old system to everything being lower case headers leads to a lot of bugs. https://github.com/cockpit-project/bots/commit/3cdbaa6d6765a... https://github.com/edwardspec/mediawiki-aws-s3/issues/49 https://github.com/firecracker-microvm/firecracker/pull/3006 https://github.com/snapview/tungstenite-rs/pull/267