News for hackers. Stuff that matters.

A comment on Debugging memory corruption: who the hell writes “2” into my stack? (2016). Parent comment

Re:Debugging memory corruption: who the hell writes “2” into... by bullen on Sunday November 14, 2021 @06:25AM (#29216624)
So if your client has one thread for networking why use non-blocking?

The age is relative, sockets are from the 70s, non-blocking is 2000+ and in most languages it's only stable since 2010+.

[ Parent | on HN ]
Re:Debugging memory corruption: who the hell writes “2” into... by nikanj on Sunday November 14, 2021 @07:07AM (#29216752)
Overlapped (=async) IO has been in Windows since NT came out, so mid-90s. I don't even know what you mean with "most languages". Most programming languages are only stable since 2010+ anyway, we get more languages every year.
[ Parent | on HN ]
Re:Debugging memory corruption: who the hell writes “2” into... by Jensson on Sunday November 14, 2021 @04:34PM (#29220954)
> So if your client has one thread for networking why use non-blocking?

No, the client would have one thread for everything, not one thread for networking. You shouldn't do blocking IO if you only have one thread that also needs to do other things.

[ Parent | on HN ]