sozu VS ws-tool

This is interesting, thank you.

I really should learn from BEAM and the OTP and learn Erlang. I get the feeling it's super robust and reliable and low maintenance. I wrote a userspace multithreaded scheduler which distributes N lightweight threads to M kernel threads.

https://github.com/samsquire/preemptible-thread

I recently wrote a JIT compiler and got lazy compilation of machine code working and I'm nowhere near beginning optimisation

https://github.com/samsquire/compiler

How do you write robust software, that doesn't crash when something unexpected goes on?

I looked at sozo https://github.com/sozu-proxy/sozu

and I'm thinking how to create something that just stays up and running regardless.

It's AGPL licensed which for a proxy is a strange choice. They have an unanswered question for months on what it might mean: https://github.com/sozu-proxy/sozu/issues/764

Without an answer to that if you use this and you need to make any change to it (even a tiny bug fix), you're basically opening yourself up a pile of legal issues.

Sozu: Well documented, runtime configurable proxy

https://github.com/sozu-proxy/sozu https://github.com/sozu-proxy/sozu/blob/main/doc/design_motivation.md

Could sozu or rathole or leaf or exodus somehow help?

it is not sufficient: a listen socket has its own queue of new TCP connections (that were already handshaked by the kernel), so dropping the listen socket drops the queue. The right way is to start the new server, transfer the listen socket from the old server to the new one with SCM_RIGHTS, then start accepting again from the new instance. That's how it is done in the sozu HTTP proxy (which also uses SO_REUSEPORT to launch multiple work processes each with their own listeners, to improve performance and isolate failure)

BTW that traffic will be coming from our sozu load balancers, built in Rust too ;)

How does it compare to sozu?

ws-tool is a high-performance websocket library that provides synchronous and asynchronous IO interfaces.

Thanks for open sourcing it, looks really interesting! Can you perhaps include in https://github.com/PrivateRookie/ws-tool in the benchmarks? From the dev perspective, what would you say why https://github.com/nurmohammed840/websocket.rs is a few ms faster? I'm interested in good perf patterns but am a beginner in Rust so it would be interesting to hear some feedback from the authors themself. Again, thx for all the work. Looks like we can finally compete with c++ WS clients.

ws-tool 0.7.0 is released, bringing permessage-deflate extension and more performance and API optimizations.

Maybe try the websocket library I implemented, ws-tool, it support tls, http/socks proxy and both sync/async api, it's performance it's pretty good.

check ws-tool/README for more information

I wrote a web socket client/server toolkit ws-tool. Util 0.4.0-beta, it support blocking & async api, http/socks5 proxy and self signed certs(powered by rustls).

If you want to manual operate bytes, bytes is a good choice, it provides traits for working with buffer and supports no_std feature. I used to impl websocket protocol with bytes, ws-tool, may be it's a example of using bytes. If you prefer high level parsing tool, nom is my recommend, it has stream parse apis, which may fit your demand, it also support no_std featrure!