• Phoenixz@lemmy.ca
      link
      fedilink
      English
      arrow-up
      10
      ·
      5 days ago

      That’s a protocol, not a software library

      TCP does what it does pretty well, no need for replacing that which works fine

      • The_Decryptor@aussie.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 days ago

        Ehh, TCP has issues with mobile connectivity and is designed around the idea that 1 logical application stream should map to 1 TCP connection, which causes issues.

        But that’s why we’ve got QUIC now.

        Other than that though, TCP is fine. If all you need is simple in-order delivery of a stream of bytes it’s hard to beat.

      • zr0@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        7
        ·
        5 days ago

        And tell me again exactly what the difference is between a protocol and an api, when both are using software that has not been changed for decades? Just curious.

        Besides that, TCP/IP is the worst thing ever for a large network and it only gets worse by the day.

      • zr0@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 days ago

        No.

        TCP/IP has 4 layers. You are probably referencing the OSI model. The OSI model is also from the 80’.

        • MonkderVierte@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          3 days ago

          With “layers”, i meant “stuff around it” for functioning, like a onion. This one fits perfectly:

          Standards

          There’s also a protocol to mark trustworthy DNS partner servers btw. Which blew up in Germany a few days ago.