Another important difference: UDP can't be used in the browser =(
Couldn't you potentially use something like WebRTC to get UDP functionality in the browser?
UDP vs TCP
11–20 of 198 posts
Re: UDP vs TCP
#12> they may arrive out of order, be duplicated, or not arrive at all!
This is first time what I read that datagram can be duplicated. Is it true? It's duplicated by network or does it mean that peer send it again?
Re: UDP vs TCP
#13> they may arrive out of order, be duplicated, or not arrive at all! This is first time what I read that datagram can be duplicated. Is it true? It's duplicated by network or does it mean that peer send it again?
Packets can be duplicated by faulty routers and loops in the topology. Happens all the time to me when I'm lost with iptables.
Re: UDP vs TCP
#14> they may arrive out of order, be duplicated, or not arrive at all! This is first time what I read that datagram can be duplicated. Is it true? It's duplicated by network or does it mean that peer send it again?
It can also be "duplicated" if you have some sort of acknowledge and retransmission on top of UDP itself. If the ack gets lost on the way back to the original sender it'll send another (probably) identical packet.
Re: UDP vs TCP
#15The main difference between TCP and UDP, as this programmer discovered, relates to quality of realtime service. Times to use UDP over TCP * When you need the lowest latency * When LATE data is worse than GAPS (loss of) in data. * When you want to implement your own form of error correction to handle late/missing/mangled data. TCP is best when * You need all of the data to arrive, period. * You want to automatically m…
Another article on this site addresses TCP plus UDP mix. The tl;dr is that they should not be used at the same time because TCP retransmission will interfere with UDP (and routers give TCP priority). As long as TCP happens outside of the "hot" loop, it's fine.
> (and routers give TCP priority).
What routers? Is this something that stupid routers did in the '90s and people are still worried about, or are modern routers actually behaving this way? (And if so, why?)
TCP retransmission interfering with UDP sounds like something that shouldn't be a problem on any sane network, especially if the application authors are smart and use something like LEDBAT for their TCP traffic when they're also doing latency-sensitive UDP communication.
Re: UDP vs TCP
#16> they may arrive out of order, be duplicated, or not arrive at all! This is first time what I read that datagram can be duplicated. Is it true? It's duplicated by network or does it mean that peer send it again?
At network level, this is common for broadcast addresses. And also if a switch floods the packet across all its interfaces if it cannot make a routing decision. At app level, this is because the app decided to retry I.e app logic.
Re: UDP vs TCP
#17Another important difference: UDP can't be used in the browser =(
Well, neither can TCP.
Re: UDP vs TCP
#18Re: UDP vs TCP
#19Do you want to hear a joke about UDP?
You might not get it, but I don't really care.
Re: UDP vs TCP
#20Do you want to hear a joke about UDP? You might not get it, but I don't really care.
Here's a joke about TCP.
Here's a joke about TCP.
Here's a joke about TCP.
Here's a joke about TCP.
Here's a joke about TCP.
> ACK