Post #2768156
2023-12-12 14:58 UTC
@ck@chaos.social @Mer__edith@mastodon.world You're explaining this at several levels of simplification below what would be relevant to me...
Replies (1)
-
@dalias@hachyderm.io 2023-12-12 15:01
@ck@chaos.social @Mer__edith@mastodon.world Specifically, I'm asking what kind of polling they're doing, and why, when the standard correct way to do this kind of operation is sleeping (in the confusingly named poll function) waiting for input on a socket, where the kernel is responsible for waking you only once input is available. There are hideous NAT connection dropping issues related to this, but solvable with a mix of TCP keepalive (also kernel side, so virtually free) and waking & reconnecting on closed sockets.