Took me forever to find this info and someone to explain it like you did...I'm a carpenter by trade..lol You did a great job ! I've been teaching myself Linux and python for a couple years now. Things are starting to click . Thanks again for the video.
Excellent tutorial! At 11:00, I liked the clarification regarding two different file descriptors ("socket" file descriptor and "accept" file descriptor). Thanks a lot.
Really appreciate the clarification on the server side of the two different fd's. I think that was muddy in my head and now with the diagram and your explaining the difference, it all makes more sense!\
Loved it. Thanks. Walk through a door and look like an idiot, would you have expected this in a video that discusses Socket API? I laughed out so loud.
Doubt: the tcp handshake that happens between the client and server is happening on the listen stage or on each accept stage? can you explain this if possible or direct me to a resource from where i can understand this better. Thanks for the amazing explaination.
5:48 'As application developers we don't need to know how it works, just that it does', lol what? Who knows how it works then if not application developers? This is probably why so many aiming for entry level position have trouble landing work... "Uhm sorry sir I don't know how it works just that it does - that'll be $75/hour please" - If i google how to install a door I generally am expecting the tutor to know how to install a door. Is there an analogy for the difference in unix and af_inet sockets? At my next programmer interview I just answer each problem with 'click download', cheers!
This is probably the most in-depth (and clear) explanation of sockets I've seen yet.
Thank you very very much.
Took me forever to find this info and someone to explain it like you did...I'm a carpenter by trade..lol
You did a great job !
I've been teaching myself Linux and python for a couple years now.
Things are starting to click .
Thanks again for the video.
PLEASE DO NEVER STOP PUBLISHING VIDEOS ! MERCI
Excellent tutorial! At 11:00, I liked the clarification regarding two different file descriptors ("socket" file descriptor and "accept" file descriptor). Thanks a lot.
Best explanation of this topic and that too in a very simple manner .. thanks a ton
Really appreciate the clarification on the server side of the two different fd's. I think that was muddy in my head and now with the diagram and your explaining the difference, it all makes more sense!\
By Far the Best Explanation Ever for Socket File Descriptor in UNIX...❤️❤️
Unrelated but this helped me a lot understanding how netpoller in Go works. Thank you so much sir for making this video
I really like the way you explain (: cheers from Argentina!
Best explanation so far....
the way you explain is so satisfying and slayinggggg
Thank you for this clear explanation. You made a hard concept very clear to me. Just clicked in my head. I have a big AHAAA!!! thank you again!
Beautiful & Unbelievable, how on earth you made it so simple !!!!
Great analogies! Please keep them up 🙏🏻
Great video, I really like the analogies it helps a lot !
Loved it. Thanks. Walk through a door and look like an idiot, would you have expected this in a video that discusses Socket API? I laughed out so loud.
Excellent explanation, good Sir.
nice explanation man, keep up the analogies!
Very clear explanation, thank you very much.
Doubt: the tcp handshake that happens between the client and server is happening on the listen stage or on each accept stage? can you explain this if possible or direct me to a resource from where i can understand this better.
Thanks for the amazing explaination.
Would love to watch videos on how the things work under the hood. Carpenter ❤
Amazing explanation.
Thanks for the great explanation
By far the BEST Video
Nice explanation
Very good video, thank you very much.
Just amazing, nothing more than I can say
I'm smarter after watching this. Thanks :)
Very good. keep going. Thanks.
I have few words: crystal clear
Great explanation, thank you!
This is a TCP/ICP socket instead of a Unix Domain socket?
Thank you so much!! Amazing explanation!!
bind(), listen() and accept() looks similar, what are the cases they're not used together?
Pretty nice, Thank you
simply the best 👏🏾
Thank you sir!
what is the name of the book please ?
the painel is cool but linux is kernel not system and sockts not created for att and master dennis ritchie in berkeley or openbsd,
Thanks
Nicee
fifo first in first all a one "type" of "primitive" os sockets api berkeley showing in bsd 4.2.2
5:48 'As application developers we don't need to know how it works, just that it does', lol what? Who knows how it works then if not application developers? This is probably why so many aiming for entry level position have trouble landing work... "Uhm sorry sir I don't know how it works just that it does - that'll be $75/hour please" -
If i google how to install a door I generally am expecting the tutor to know how to install a door.
Is there an analogy for the difference in unix and af_inet sockets?
At my next programmer interview I just answer each problem with 'click download', cheers!