Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
SortOfTested24464303dThe second rule of networking: Speed at all costs, especially in the datacenter
Fast-Nop36227303d@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.
Nanos11043303dI'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 ?
Fast-Nop36227303d@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.