• neeeeDanke@feddit.de
    7·
    11 months ago

    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.

    • pivot_root@lemmy.world
      0·
      11 months ago

      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.

    • CmdrKeen@lemmy.today
      0·
      11 months ago

      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.

  • IHeartBadCode@kbin.social
    1·
    11 months ago

    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.

  • 👍Maximum Derek👍@discuss.tchncs.deEnglish
    1·
    11 months ago

    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.

    • bleistift2@feddit.deEnglish
      1·
      11 months ago

      You forgot to mention that you might get it twice, or thrice, or more, and in different versions.

      • Neato@kbin.social
        0·
        11 months ago

        (novice) Why would you get UDP packets multiple times? UDP doesn’t check for acceptance I thought.

          • PowerCrazy@lemmy.ml
            0·
            11 months ago

            That is extraordinarily rare and I’m not even sure if it’s possible anymore. That was potential attack vector in the 90’s where you have a port on network switch, and then you flood the cam table with thousands of bogus mac addresses until you fill it up, then the switch turns into a hub, and you can now sniff all traffic traversing the switch. These days I’m not sure what will happen if you do successfully fill up a switches cam table. Also cam table sizes are are much much larger now. ~128k entry’s vs maybe 1000 back in the day.

    • frezik@midwest.social
      0·
      11 months ago

      It’s a postcard saying “hey, thinking of you!” and there’s a picture of a wulrus on it.