mirror of
https://github.com/brazilofmux/tinymux
synced 2026-08-13 00:23:11 -04:00
No description
2f1399c80d
client/tf never set TCP_NODELAY, so the client side of every session ran with Nagle enabled. Client companion to #2194, which was the same gap in the server's POSIX engines. A single typed command is immune either way: send_line() assembles command + CRLF into one buffer and issues one write(). But anything that sends several lines in one event-loop pass -- a trigger firing off a match, a macro or keybinding bound to multiple commands, a scripted burst, a speedwalk -- produces back-to-back small writes, and Nagle makes each one after the first wait for the ACK of its predecessor, which the peer's delayed-ACK timer can hold for up to ~40ms. Against a remote server the burst then leaves the client at ACK cadence instead of departing together. Invisible on loopback, which is why local testing never showed it. Set after the connect loop rather than at either `break`, so both paths (immediate connect and EINPROGRESS + poll) are covered by one call. Non-fatal: a latency hint failing is no reason to refuse a connection that otherwise works. Verified by strace'ing tf under a pty against a scratch netmux: setsockopt(4, SOL_TCP, TCP_NODELAY, [1], 4) = 0 Catch-verified: with the change reverted, tf makes no setsockopt call at all on the connect path. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| client | ||
| color | ||
| debian | ||
| docker | ||
| docs | ||
| hooks | ||
| mux | ||
| parser | ||
| ragel | ||
| sgp | ||
| specs | ||
| testcases | ||
| tests | ||
| tools | ||
| unix | ||
| utf | ||
| win32 | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| CONTRIBUTING.md | ||
| dounix.sh | ||
| dowin32.sh | ||
| GEMINI.md | ||
| LICENSE | ||
| Makefile | ||