Live data from Hacker News

"A sleep(1) is put into all SSL_read() and SSL_write() calls..."

bugs.python.org

51–52 of 52 posts

Re: "A sleep(1) is put into all SSL_read() and SSL_write() calls..."

#51
post #48
post #42

Earlier quoted context omitted.

I really don't think you've ever seen BSD return in milliseconds after a 1-second sleep. Respectfully, I think you're pretty much just wrong.

Well, that is not what I meant at all, I meant that I've seen BSD return in say 2 microseconds after calling usleep(1). But that's usleep not sleep, which is the inaccuracy I was admitting to in the first place.

Ok, but (a) this article is talking about literally POSIX sleep(3), and (b) there is a ton of confusion on this thread about whether sleep is ms-denominated or seconds-denominated.

Sorry to pile on you, though.

Re: "A sleep(1) is put into all SSL_read() and SSL_write() calls..."

#52

Earlier quoted context omitted.

Additionally I think you'd be hard pressed to find a modern compiler (for some loose definition of modern) which would not optimize that loop away.

At that point they would just turn on the optimizations as an "insurance".

Don't you mean off?
Post reply on HN