Nah, not a noob question at all! tcp vs http trips up everyone at first.
HTTP’s just a protocol that *uses* TCP. Like how Netflix uses your internet—you don’t need to know how the cables work to binge-watch.
But if you’re optimizing a high-traffic site, TCP settings (like keepalive) can save your bacon. `netstat -tuln` is your friend here.
HTTP’s just a protocol that *uses* TCP. Like how Netflix uses your internet—you don’t need to know how the cables work to binge-watch.
But if you’re optimizing a high-traffic site, TCP settings (like keepalive) can save your bacon. `netstat -tuln` is your friend here.
