News for hackers. Stuff that matters.
Re:Hooray for the Sockets Interface by zbentley on Wednesday July 29, 2026 @11:36AM (#49098899)
I suppose, but the number of applications for whom a successfully-negotiated bare socket connection (with no TLS or data exchanged) is side-effectful to the point that this causes problems is pretty darn small. I'm sure there are some terrifying counterexamples, but they have to be part of a tiny minority, right?

More concerning is the risk of exhausting server socket resources when probe-based connects don't hang up quickly if they don't want to use a connections. Lots of servers/load balancers aren't well-tuned to force-close connections if the first byte doesn't arrive within a short time.

Re:Hooray for the Sockets Interface by drdexebtjl on Wednesday July 29, 2026 @01:05PM (#49100128)
I agree. But we couldn’t have possibly guessed this in the 80s.

Instead we converged on a very simple primitive that makes no such assumptions and can be composed into a wider variety of high level abstractions in user space.

Re:Hooray for the Sockets Interface by cyberax on Wednesday July 29, 2026 @05:17PM (#49103211)
> More concerning is the risk of exhausting server socket resources when probe-based connects don't hang up quickly if they don't want to use a connections.

TCP connection cookies solved this problem in 90-s! They fell out of use because dedicating a couple MB of RAM to track a few hundred thousand connections is not a big deal anymore.

Re:Hooray for the Sockets Interface by inigyou on Wednesday July 29, 2026 @07:07PM (#49104257)
Linux will still revert to cookies when exceeding a certain number of half open connections, preventing DoS.