Lots of wisdom on this page ;) Just want to add. Real-world, often the predominant use case is not optimizing for "max-conns". But <100,000 concurrent users, w

Lots of wisdom on this page ;) Just want to add. Real-world, often the predominant use case is not optimizing for "max-conns". But <100,000 concurrent users, who instead need to be connected for a very long time. In this instance, I've found Caddy's websocket directive, inspired by Websocketd, to be quite robust and elegant. It's just a process per conn. Handling stdin, stout style messaging ;)