The first rule of networking: You can't claim that a message had been received until you have heard the reply.

  • 1
    The second rule of networking: Speed at all costs, especially in the datacenter

    #UDP-wrapped-TCP 😎
  • 1
    @SortOfTested My use case is voice over websocket, which is TCP, because I was way too lazy to figure out how WebRTC works and because the browser APIs all work with TCP.
  • 3
    @homo-lorens For any kind of streaming, TCP sucks because the delay introduced by retransmission is worse than a lost package. Classic case of a cure being worse than the disease.
  • 0
    I'm reminded of package I know that falls over the moment there is an error at the other end, since it assumes everything is always perfect.

    Give it a laggy connection, and it falls apart it no time.

    Which reminds me of a question I had, which I don't seem to remember ever finding out the answer to, that someone here might know..

    If you send data via SSL does that automatically include error correcting to prevent data loss ?

    Related link:

  • 1
    @Nanos Of course it does because it's based on TCP which abstracts an unordered and lossy connection into an ordered and lossless one. See also the OSI model for general orientation, though TCP/IP doesn't conform to the OSI layer model 1:1.

    However, all abstractions are leaky at some point, and connection errors can still pop up e.g. if the cat rips out the cable.
Add Comment