Comment by syncsynchalt
2 years ago
Ironic since Nagle's Algorithm (which TCP_NODELAY disables) was invented for interactive sessions.
It's hard to imagine interactive sessions making more than the tiniest of blips on a modern network.
2 years ago
Ironic since Nagle's Algorithm (which TCP_NODELAY disables) was invented for interactive sessions.
It's hard to imagine interactive sessions making more than the tiniest of blips on a modern network.
Isn't video calling an interactive session?
I think that's more two independent byte streams. You want low latency but what is transfered doesnt really impact the other side, you just constantly want to push the next frame
Thanks, that makes sense!
It's interesting that it's very much an interactive experience for the end-user. But for the logic of the computer, it's not interactive at all.
You can make the contrast even stronger: if both video streams are transmitted over UDP, you don't even need to sent ACKs etc. To be truly one-directional from a technical point of view.
Then compare that to transferring a file via TCP. For the user this is as one-directional and non-interactive as it gets, but the computers constantly talk back and forth.
2 replies →
You're right! (I'm ignoring the reply thread).
I'm so used to a world where "interactive" was synonymous with "telnet" and "person on keyboard".