UDP as a transport protocol is used in situations where speed is more important than reliability in the delivery of the packets. Therefore, any application that requires speed as its primary delivery could use UDP. This type of delivery is not checked for consistency or reliability, so you wouldn't use it if the delivery has to be reliable.
tcp
It is possible for an application to enjoy reliable data transfer over UDP. UDP uses checksum to learn whether data reached is true or not. You can also ensure reliability by creating a private protocol built on UDP.
UDP can be used in many applications for transport, not just a single application. UDP is commonly used when speed is more important than reliability in the transfer.
You don't need to configure UDP; this is done automatically by the application protocols that use this transport method.
1. IP works at network layer, UDP works at transport layer. 2. UDP carries application data, IP carries TCP segments or UDP datagrams.
UDP is alot faster than TCP. So if its realtime obviously it has to be fast, thus UDP. The only problem is UDP isn't as reliable or as secure as TCP. But it does have the speed advantage.
UDP does not require as much resources as TCP but in the same time, it does not insure delivery of packets.
Why_an_application_developer_might_choose_to_run_an_application_over_UDP_rather_than_TCP"send me
UDP: DNS, TFTP, DHCP... TCP: SMTP, HTTP, HTTPS, DNS, FTP, SHH, Telnet...
Application Layer
What a client application usually selects for a TCP or UDP source port number is a random value. The value selected is generally in the range of the registered ports.
Write and run a client and a server program in C-language using UDP