by dedalus on 3/23/2016, 5:25:17 PM
by nickpsecurity on 3/23/2016, 3:51:33 PM
I tell people to start with UDT when trying to improve TCP or UDP:
Good chance they already did what you need. On supercomputers with a distributed filesystem (Sector/Sphere) at that. :)
by tokenrove on 3/23/2016, 12:12:08 PM
Sadly no mention of SCTP, which, if you don't need to communicate with arbitrary hosts over the Internet, sits in a nice middleground between TCP and UDP.
by FullyFunctional on 3/24/2016, 9:29:00 PM
TCP and UDP aren't the perfect solutions [for everything] and there's no shortage of proposed alternatives to TCP; Besides already mentioned QUIC, there's CurveCP (https://curvecp.org/), MinimaLT (https://www.ethos-os.org/), or even more extreme Named Data Networking (http://named-data.net).
For a background on why TCP is this way, look up "The Design Philosophy of the DARPA Internet Protocols", by David D. Clark, however knowing is little comfort.
https://en.wikipedia.org/wiki/Reliable_User_Datagram_Protoco... is also a good protocol in this space.
Its been a decade since I worked with atou (Almost TCP over UDP) but it does work: http://www.csm.ornl.gov/~dunigan/net100/atou.html
An excellent read on how to implement reliable UDP by Craig is here: https://pdfs.semanticscholar.org/1d88/1d58d53ee530a4b4c7427a...