dotCooCoo 7d4bc14c1d Control server: refused connections drain on their own threads ...

The accepting thread drained each connection it refused as busy for up
to 250 ms before accepting the next, so refused peers that stayed
connected without writing delayed every connection after them. Each
drain now runs on a thread of its own, up to 16 at once; past that, a
refused connection gets the busy reply and is closed without a drain.

connection_limit_refuses_then_frees_slot now uses a 30 s idle timeout:
its first client sends nothing, and under load the 300 ms timeout
closed it before the third client connected.

2026-10-24 08:23:14 -07:00

..

deckcraft

Control server: refused connections drain on their own threads

2026-10-24 08:23:14 -07:00

deckcraft-cli

refactor: replace redundant closures with method paths (SonarCloud S1612) (#1261)

2026-10-24 04:27:07 -04:00

deckcraft-web

Merge the landing branch into land-r6

2026-10-14 15:14:21 -04:00