View RSS Feed

Java Socket


Rate this Entry
by , 04-25-2012 at 11:34 PM (964 Views)
UDP & TCP work different to some extent.When data is being sent through TCP, first of all a connection is created. Once TCP connection gets established, it is guaranteed by TCP that data would be reaching the other end for sure, or error will be occurred.

Only datagram i.e. packets of data is being sent by UDP to the network’s IP address. There is no guarantee that data reaches. Also, no guarantee is there regarding order in which these packets of data would be arrived at receiver. It shows UDP consists of low protocol overhead as compared to TCP.

UDP is considered appropriate to transfer the data where if packet gets lost in transition then this is not a big matter. For example, Let us imagine the live TV signal transfer at the web. Signal shall be reached to clients as closer to the live as it could be possible. Hence, if one or two frames are lost, there is nothing as such to worry about. One doesn’t want to see live broadcast to get delayed so that make it sure that frames have been shown to client. Missed frames

Submit "UDP vs. TCP" to Facebook Submit "UDP vs. TCP" to Digg Submit "UDP vs. TCP" to Submit "UDP vs. TCP" to StumbleUpon Submit "UDP vs. TCP" to Google

Tags: udp vs. tcp Add / Edit Tags