Vitaly Shukela

Websocat4 should not exit on zero-length messages by default (except of with `seqpacket:`, for which it may cause the recipient to exit), so `--no-exit-on-zeromsg` may be less applicable. A dummy...

Like Websocat1, Websocat4 applies automatic transformations to the arguments you use. `--no-fixups` may be added to inhibit this step, which would typically lead to errors, unlike in Websocat1 where it...

Websocat1 contains a mode where it automatically closes the connection after a single message. Such overlay can easily be added to Websocat4 (though it would work only with datagram-oriended Sockets)....

Like Websocat1, Websocat4 attempts to serve multiple connections (including in parallel) when you specify a listening socket at the left side. However, `--oneshot` option to explicitly limit it to one...

Both Websocat1 and Websocat4 reply to pings, but Websocat1 can also send pings periodically. This includes additional features like printing RTTs for resulting pong replies or stopping outgoing pings after...

Websocat1's subprocess executors typically waits for child process termination before considering connection as really closed. Websocat4's subprocess module is currently simpler in this regard. `--exec-exit-on-disconnect`-like behaviour may be default now,...

On UNIX-like platforms, Websocat1's subprocess executor can send `SIGHUP` to processes when associated connection gets closed. In Websocat4 it is not yet implemented (maybe the process is just killed instead,...

Websocat1 have `-v` and `-q` to affect verbosity of diagnostic output. Websocat4 has `RUST_LOG` support, but no relevant CLI options at the moment. Making non-debug, user-friendly logs is not in...

Websocat1 contains `reuse-broadcast:` (alias `reuse:`) and `reuse-raw:` overlays. Websocat4 does not yet. This includes various additional options that affect details of reuser behaviour. `reuse-raw:` **implemented** in `4.0.0-alpha2`.

Unlike Websocat1, Websocat4 makes use of WebSocket continuation frames and does not need to cache the whole message in memory, so buffer size should not affect maximum line length. Lines...