Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / 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 |
Post New Answer View All Answers
What is active unix domain sockets?
What is af_inet in socket?
Why do I get EPROTO from read()?
How do I use TCP_NODELAY?
How can I write a multi-homed server?
What's the difference between a socket and a port?
Is there any advantage to handling the signal, rather than just ignoring it and checking for the EPIPE error? Are there any useful parameters passed to the signal catching function?
Can multiple sockets use the same port?
What is a socket file?
Can a socket have multiple ports?
Why does the sockets buffer fill up sooner than expected?
What's better 6pt or 12pt sockets?
What is a deep well socket?
Are sockets files?
Is a socket a file?
