Answer Posted / r.n.achary

You have to design your protocol to expect a confirmation
back from the destination when a message is received. Of
course is the confirmation is sent by UDP, then it too is
unreliable and may not make it back to the sender. If the
sender does not get confirmation back by a certain time, it
will have to re-transmit the message, may be more than
once. Now the receiver has a problem because it may have
already received the message, so some way of dropping
duplicates is required. Most protocols use a message
numbering scheme so that the receiver can tell that it has
already processed this message and return another
confirmation. Confirmations will also have to reference
the message number so that the sender can tell which
message is being confirmed. Confused? That's why I stick
with TCP.

How reliable is udp?

905

---

Normally they r setting question 4rm time@distance,time@work,ages,cisterns@pipes,etc

2493

---

Does fortnite use tcp or udp?

1268

---

What is difference between tcp and udp socket?

937

---

Why tcp is more reliable than udp?

1084

---

Is tcp faster than udp?

1032

---

Why tcp is better than udp?

1003

---

Is udp faster?

967

---

Is udp better than tcp?

898

---

Can tcp and udp share the same port?

947

---

Does netflix use udp or tcp?

1045

---

What is the advantage of udp over tcp?

1038

---

Is port 80 udp or tcp?

991

---

Is tcp or udp better?

911

---

A signal with 300 milliwatts power passes through 10 devices, each with an average noise of 3 microwatts. What is the SNR? What is the SNRdb?

4549

---