***** Bro in my book Computer Network by Andrew S. Tanenbaum UDP have 8 bytes header and TCP have 20 bytes header which is correct as we are comparing both the protocols. yeah IP header is 20 bytes for both because It has to be same you are comparing the message that have been delivered and he is talking about the packet header of these two protocols only without including IP header so he is also right. correct me I am wrong. :)
As everyone's saying, great video! Have an exam tomorrow, saved a lot of time by watching this, couldn't really understand it from only texts. So THANKS! :)
Dear Pieter, I did a test to work in the public sector and one of the questions was to describe how TCP / IP works, and certainly this video help me a lot with this question. Thank U.
I am one of the "mentally handicapped" that actually find the speed of the video optimal for me :) Please keep it up, most people on RU-vid talk way too fast
Great question. Originally BitTorrent only ran over TCP. In 2008, the µTorrent team developed µTP, a UDP-based protocol for BitTorrent. Since UDP doesn't offer in-order delivery (among other things), µTP implements this functionality in its application layer. If you want to read more about how and why BitTorrent runs over UDP, you can find some relevant links in the video description.
+Oliver Reipschläger I'm actually a Belgian man pretending to be a British person trying to fake an American accent. And you totally fell for it... MUAHAHA!
+PieterExplainsTech I had no idea you were from Belgium. I speak dutch as well, and my english accent is horrible so, good job on both your English and the Tutorial :D
+PieterExplainsTech I could hear a bit of the accent coming out, but that is the best American I have heard so far coming from a non-English speaking person.
Thank you so much for making these videos. Incredibly helpful. I bet there is a sizable boost in general productivity from exceedingly informitive videos like this
Almost all the comments here tell the same thing, Its an amazing video. I do want to point out the example that you mentioned for TCP and UDP, it just cleared the concept for me. Thanks.
Great work! Thank you very much. I was told about this topic for hours and hours at school, did not get it. Here you come and in 11 minutes I DO understand. Hats off, and keep the vids coming :)
UDP and IP have different tasks and are often used together. IP helps deliver packets to the right computer. Transport protocols like UDP help deliver packets to the right application on that computer. If we didn't have transport protocols, you wouldn't be able to use Chrome and Dropbox at the same time.
Your videos are great! And incredibly informative! I appreciate the effort put into making the videos. You are VERY easy to understand too! Good job, hope to see more videos soon :)
Thank you very much for the video man! I realize the audio was slow but it gave me time to process and understand the details! You do a great job at explanations with audio and the video components! Its amazin eh! Cheers! Love from Canada!
Very good video, formal, animated, good sound, high quality, finally a respectable video, thank you so much, this is a good start to further investigation about, for example what contain the headers of segments, how TCP corrects the lost of packages...etc. It could be nice to see this explanation in this kind of videos.
This and your other videos are gorgeous! Can you pls make others where you explain the complete 5 layers of the "internet connection"? It would be really nice because when I look in the internet, everybody explains it different that it's really hard to understand :/
UDP: Small Packet Size Connectionless May arrive out of order No error recovery Message-oriented Sends messages in chunks TCP: Stream oriented Sets up 3 way handshake In-order delivery Congestion control Bigger header Not always sent immediately
Thanks bro, I'm brazilian and I need learn this informations, I don't understand English very well, but, thank you I'm learning more that my brazilian teacher and look he speak in Portuguese, so thanks man!!! You're awesome.
I appreciate how you say "UDP is snailmail, email, or text messaging" Then go on to say "When text messaging, TCP obviously takes the cake" WHICH IS IT JESUS CHRIST
In hindsight, the way I compared the two was pretty confusing. When it comes to sending text (an e-mail, chat messages, etc), you want to make sure that all of your words arrive. You also want to make sure that they arrive in the correct order. You also want some assurance that some of your words can't accidentally turn into gibberish. TCP offers facilities for that. UDP doesn't. Now here's the confusing bit. I said that UDP is message-oriented because it considers data as separate, distinct chunks. I was looking for an analogy to explain the difference between distinct chunks (UDP) and a continuous flow of data that is treated as one thing (TCP) when I compared sending distinct chunks to sending e-mail messages. Let's try this instead: message-oriented is like lots of waterdrops whereas stream-oriented is like a river. Both consist of water (network packets) but in the case of the river, the water is "grouped" into something bigger. Hope that helps!
Thank you! Some services like DNS can run over UDP as well as TCP, but I can't come up with an example of one transport protocol being wrapped in the other. What do you think the benefits would be of wrapping TCP traffic in UDP packets or vice versa? I can't think of any right now. I only see more communication overhead.
