sdomi changed the topic of #http.sh to: the coolest web framework (in Bash) to date :: logs: https://libera.irclog.whitequark.org/http.sh/ :: contributions welcome <3
<sdomi> surprisingly: `echo -n a; echo -n b` is *always* two TCP packets with ncat/socat, while `echo -n ab` is one
<sdomi> this also happens when grouping with { } (which, tbh, is the more unexpected part for me, since you can usually treat streams from those as uniform outputs)
<sdomi> anyways, I think that switching httpsh from "echo whenever we need" to "buffer everything and release when ready" may have some speed advantages
<sdomi> in other news: I'm working on making the WebSocket support in httpsh a bit nicer https://f.sakamoto.pl/IwI9K1GGg.png
<sdomi> I've refactored the way it routes them, added a custom extension for files which are supposed to be executed via WS, and basically rewrote all websocket logic to be a bit nicer
<sdomi> ... huh, turns out that with `( )` my assumption was correct, and it does buffer the output (and thus it is sent as one packet)