Data travels in packets. In a TCP connection, every packet must reach the destination before the transmission will be complete. This means that it goes back to resend packets should any be dropped. UDP does not do this. This makes it ideal for real time applications that cannot viably stop. These include VoIP and video streaming.
[Above answer is right, UDP is used in the situations where partial or little data loss is bearable such as VoIP, Video Streaming, you might have experienced it many times when browsing YouTube videos. Many of peer to peer applications use this service. It doesn't guarantee the loss-free transmission of data, as TCP does. It does use to provide the current user facility to push as much data as he can on the link, without caring about others. Most of today's applications which used to use UDP has now been transferring to TCP. A good example of it is bit-torrent ]
DNS uses both TCP and UDP, also a lot of online chats use UDP. I think even when you want videos on YouTube UDP is used to deliver video and audio.
UDP and ports 67 and 68.
UDP is a connectionless protocol, so there is no session to close. UDP is not expecting any particular packet, so opening and closing via UDP is not necessary.
You don't need to configure UDP; this is done automatically by the application protocols that use this transport method.
Aknowlagement
Yes, it does.
TCP
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.
No it uses UDP packets.
Yes, most often.
UDP does not require as much resources as TCP but in the same time, it does not insure delivery of packets.
138