Answer Posted / sudheer

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, maybe
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.

Is udp better than tcp?

898

---

Why tcp is more reliable than udp?

1084

---

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

---

Is tcp or udp better?

911

---

Is udp safe?

1009

---

Does netflix use udp or tcp?

1045

---

What are advantages and disadvantages of combining the session presentation application layer in the osi model into one single application layer in internet layer?

7293

---

Is port 8000 a tcp or udp?

1070

---

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

2493

---

Why is udp unreliable?

932

---

How reliable is udp?

904

---

Which is better tcp or udp?

978

---

Can you send and receive on same udp port?

962

---

Is tcp faster than udp?

1032

---

Why udp is not reliable?

940

---