2 ms·
Why UDP isn't good for real-time applications: * lack of a connection * lack of order * lack of retransmission * lack of error checking * lack of flo
by peterwwillis 13y ago
Why UDP isn't good for real-time applications:
* lack of a connection
* lack of order
* lack of retransmission
* lack of error checking
* lack of flow and congestion control
* lack of integrity/security
Why TCP isn't good for real-time applications:
* latency
* latency
* latency
* latency
* latency
* latency
SCTP's only advantages over TCP for real-time applications is unordered data delivery and selective acknowledgement. In this way we can still use the most recently arrived message instead of the correct ordered one, which will reduce latency in one area.
But the 'association' is still be affected by congestion control, especially with multiple failures in the same window. Using Reno SCTP, this may be mitigated, and it is argued that some congestion control is much better than none at all. But without evidence specific to an application's implementation, UDP is still the superior real-time protocol if you don't care about what data you're getting.
- aryastark 13y agoUDP has error checking in the form of a checksum. It's one of the few guarantees UDP has: your datagram either arrives complete, or not at all. TCP also has no real security to speak of, either.