SoylentNews is people
SoylentNews
posted by
martyb
on Sunday March 27 2016, @12:27PM
from the could-this-site-run-without-both-of-them? dept.
from the could-this-site-run-without-both-of-them? dept.
Discussion on the advantages of TCP vs UDP (and vice versa) has a history which is almost as long as the eternal Linux-vs-Windows debate. As I have long been a supporter of the point of view that both UDP and TCP have their own niches (see, for example, [NoBugs15]), here are my two cents on this subject.
Note for those who already know the basics of IP and TCP: please skip to the 'Closing the Gap: Improving TCP Interactivity' section, as you still may be able to find a thing or two of interest.
It's a primer, or a refresher, or a skip. We have all kinds here. Enjoy, or don't.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Q: How many Martians does it take to screw in a light bulb?
A: One and a half.
(Score: 3, Touché) by Craig Cherry on Sunday March 27 2016, @05:17PM
"a history which is almost as long as the eternal Linux-vs-Windows debate"
It's worth knowing that these network standards date primarily from the minicomputer era, when the very simple PCs of the time tended to use slow point to point serial port connections.
UDP was defined in RFC768 in 1980. TCP dates from a few years earlier, so presumably the first discussions about when to use TCP versus UDP would have been in 1980.
Microsoft announced Windows 1.0 in 1983 and shipped it in 1985.
Linux started in 1991.
(Score: 0) by Anonymous Coward on Monday March 28 2016, @09:39AM
Whatever. Since all those things happened long before any of us were born, their exact chronological order only matters to pedantic historians and trivia buffs.