Nah, TCP is still just kicking the box over, but just kicking it over again, if the reciever doesn’t kick back a box saying they got it.
TCP is also deciding to ramp up the amount of boxes you kick over until the post worker gets crushed by boxes, at which point you decide to lower your box-kicking rate by half and try again.
Well yes, internally that’s what it does, but from a user perspective it just looks like being handed the package, you never see any of the failed attempts (unless delivery fails completely because the company went out of business). It’s sorta more like having a butler who orders it for you and deals with any potential BS that might happen, and then just hands you the package when it finally arrives in one piece.
Like Jim Carey in Ace Ventura?
For those that may have forgotten: https://youtu.be/WjTDXatmzUE
UDP seems more like a ball fired from canon to me. You may not be prepared for it and you won’t know what state it’s in when it gets here, but that packet is making it to the gate no matter what. Or, in the rare case it doesn’t, it means someone else is having a real bad time.
You forgot to mention that you might get it twice, or thrice, or more, and in different versions.
(novice) Why would you get UDP packets multiple times? UDP doesn’t check for acceptance I thought.
From StackOverflow:
Switches will send packets to all interfaces when using broadcasts or under extreme conditions (full MAC Address Table). This can lead to duplication if there is a loop between two or more switches and if the Spanning Tree Protocol is not used. So the answer is rarely.
https://stackoverflow.com/questions/9196791/duplicate-udp-packets-how-often-it-happens#9220574
Because you’re so prepared for a guy kicking a parcel over the fence. It’s the same analogy my dude.
I mean I’ve been trying to formally request that ISO change the C API for send() to yeet() for sockets where connection reliability is not required at the network interface level.
There’s nothing wrong with UDP. At least not that I know of.
Not really a problem with UDP itself, but with some very old protocols like DNS that rely on UDP but can’t be changed because of compatibility. If you’re writing a new service that uses UDP, there’s nothing stopping you from designing it so that it doesn’t provide an opportunity for bandwidth amplification.
Can’t understand the VPN one shouldn’t the traffic pass through the VPN and then go to the user like the ssh one …
