Click here to Skip to main content
15,847,583 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
heyy guys..


What protocol should I use? TCP or UDP? And why?

Dear Abhishek ,

Transmission Control Protocol is a connection-oriented protocol, which means that it requires handshaking to set up end-to-end communications. Once a connection is set up user data may be sent bi-directionally over the connection.

So if the network is VPN,Lan or Intranet, personally I will prefer TCP.

UDP is a simpler message-based connectionless protocol. Connectionless protocols do not set up a dedicated end-to-end connection. Communication is achieved by transmitting information in one direction from source to destination without verifying the readiness or state of the receiver. However, one primary benefit of UDP over TCP is the application to voice over internet protocol (VoIP) where any handshaking would hinder clear voice communication. It is assumed in VoIP UDP that the end users provide any necessary real time confirmation that the message has been received.

Comparisons of TCP and UDP

Reliable: TCP manages message acknowledgment, retransmission and timeout. Multiple attempts to deliver the message are made. If it gets lost along the way, the server will re-request the lost part. In TCP, there's either no missing data, or, in case of multiple timeouts, the connection is dropped.
Ordered: if two messages are sent over a connection in sequence, the first message will reach the receiving application first. When data segments arrive in the wrong order, TCP buffers the out-of-order data until all data can be properly re-ordered and delivered to the application.
Heavyweight: TCP requires three packets to set up a socket connection, before any user data can be sent. TCP handles reliability and congestion control.
Streaming: Data is read as a byte stream, no distinguishing indications are transmitted to signal message (segment) boundaries.

Unreliable: When a message is sent, it cannot be known if it will reach its destination; it could get lost along the way. There is no concept of acknowledgment, retransmission or timeout.
Not ordered: If two messages are sent to the same recipient, the order in which they arrive cannot be predicted.
Lightweight: There is no ordering of messages, no tracking connections, etc. It is a small transport layer designed on top of IP.
Datagrams: Packets are sent individually and are checked for integrity only if they arrive. Packets have definite boundaries which are honored upon receipt, meaning a read operation at the receiver socket will yield an entire message as it was originally sent.
No congestion control: UDP itself does not avoid congestion, and it's possible for high bandwidth applications to trigger congestion collapse, unless they implement congestion control measures at the application level.

If you are think about security levels and reliable data transfer also
check these links, why Udp

A UDP-based Reliable Data Transfer Library[^][^]

This will helpful to you

Thanks & Regards
Share this answer
RaisKazi 6-Jan-12 1:59am    
My 5.
Sridhar Patnayak 6-Jan-12 2:02am    
Thanks RaisKazi
Yes, agreed. But what i want is precisely how easy or difficult is it to implement either of the options.

Also, if you have an experience of making an application of similar kind, i can get a better answer.
Share this answer
Sridhar Patnayak 6-Jan-12 1:44am    
My self I am experienced with tcp and VPN, and I felt that it is much easier to implement in the suggested networks like Lan and VPN. Their are several articles which will give you information to implement tcp file transfer. And now check my modified solution, when udp is need to implement. link provided (A UDP-based Reliable Data Transfer Library).
Mehdi Gholam 6-Jan-12 2:01am    
Use the comments, do not post solutions for further assistance.
Abhishek Nandgaonkar 6-Jan-12 2:04am    
yeah sorry.. new to this site.. dint know that..

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900