rust-socketio VS essie-tls-rs

The world has moved on though to opinionated tools, and Rust isn't even the furthest in that direction (That would be Go). The equivalent of those two lines in Cargo.toml would be this example of a basic configuration from the jacoco-maven-plugin: https://www.jacoco.org/jacoco/trunk/doc/examples/build/pom.x... - That's 40 lines in the section to do the "defaults".

Yes, you could add a load of config for files to include/exclude from coverage and so on, but the idea that that's a norm is way more common in Java projects than other languages. Like here's some example Cargo.toml files from complicated Rust projects:

Servo: https://github.com/servo/servo/blob/main/Cargo.toml

rust-gdext: https://github.com/godot-rust/gdext/blob/master/godot-core/C...

ripgrep: https://github.com/BurntSushi/ripgrep/blob/master/Cargo.toml

socketio: https://github.com/1c3t3a/rust-socketio/blob/main/socketio/C...

Looks great! Was the motivation for creating this better integration with Tower? How does it compare to https://github.com/1c3t3a/rust-socketio . I haven't used either, but I was thinking about using the latter in an upcoming project. Now I am considering using this one.

So I set out to write a Socket.IO server by extending the existing crate rust-socketio.

I‘m working on the implementation of a socketio client in rust. https://github.com/1c3t3a/rust-socketio.

This week I started writing a safe TLS library for it, called Essie TLS. I read a lot and found that constant-time Rust code requires unsafe. So my plan is to use a delay timer to avoid leaking secrets via timing side-channels. This will make TLS handshakes a little bit slower. Writing a TLS library is a lot of work. TLS 1.3 is very complicated and spans about 200 pages of RFCs. But the tools are working very nicely: Rust stable, CLion, and Gitlab.com.