tcpproxy VS rustpad

Thanks. Perhaps I did go overboard with that disclaimer.. probably because I myself made the mistake of initially using [0] the oh-so-convenient tokio::io::copy() instead of writing my own copy method that would drop the other half of the connection when one side was closed.

The copy_with_abort() routine is still taking the easy way out in this not-optimized-for-heavy-production-use sample because it uses a broadcast channel per connection to reactively signal that the other half of the connection should be closed (rather than timing out every x ms to see if an abort flag has been set). In the real world, I'd probably replace the join! macro with a manual event loop to be able to do the same but without creating a broadcast channel per-connection.

(I maintain an extremely lightweight "awaitable bools" library for rust [1] that is perfect for this kind of thing (roughly equivalent to a "bounded broadcast_channel<()> of queue length 1, but each "channel" is only a single (optionally stack-allocated) byte) — but it's for event loops in synchronous code and not async executor compatible.)

[0]: https://github.com/mqudsi/tcpproxy/commit/0164ef836a49f2f738...

[1]: https://github.com/neosmart/rsevents

Take a look at https://github.com/ekzhang/rustpad

I'm looking for software similar to https://rustpad.io but with login and password. Docker would be nice :)

You could try rustpad

Looks pretty similar to https://rustpad.io/

Awesome! I requested this in rustpad but it was closed with wontfix. I suppose it is out of scope of rustpad but I'm really glad to see that there's this project to add it.

Just adding an example to the other side, I wrote https://rustpad.io/ in Rust, which is a collaborative text editor that uses WebSockets and resolves edit conflicts in real time using an operational transformation algorithm. It's a fairly complex bit of logic. But I actually thought Rust was the best language for this application because of performance, data race-safety, Serde, and the borrow checker. (My second choice would have been Go with stress tests run under `the -race flag.)