Interested to Buy Any Domain ? << Click Here >> for more details...
When should I use UDP instead of TCP?
- 1 Answers
- 2123 Views
- I also Faced
- E-Mail Answers
Answer / chaitanya
UDP is good for sending messages from one system to another when the order isn't important and you don't need all of the messages to get to the other machine. This is why I've only used UDP once to write the example code for the faq. Usually TCP is a better solution. It saves you having to write code to ensure that messages make it to the desired destination, or to ensure the message ordering. Keep in mind that every additional line of code you add to your project in another line that could contain a potentially expensive bug.
If you find that TCP is too slow for your needs you may be able to get better performance with UDP so long as you are willing to sacrifice message order and/or reliability.
UDP must be used to multicast messages to more than one other machine at the same time. With TCP an application would have to open separate connections to each of the destination machines and send the message once to each target machine. This limits your application to only communicate with machines that it already knows about.
| Is This Answer Correct ? | 0 Yes | 0 No |
How many sockets can a cpu have?
What are Sockets?
Why do I keep getting EINTR from the socket calls?
What is difference between socket and websocket?
How do I properly close a socket?
What exactly does SO_REUSEADDR do?
When should I use shutdown()?
Can a socket have multiple ports?
Why does connect() succeed even before my server did an accept()?
How can I set the timeout for the connect() system call?
What is the difference between connected and unconnected sockets?
How can I listen on more than one port at a time?
Unix Commands 
