For anyone wondering, AF_INET is for IPv4 type addresses not TCP or UDP. AF_INET6 is used for IPv6 addresses. Only the _type_ parameter of the socket function is responsible for determining if it will be TCP or UDP.
Great video! I have previously done work with sockets in python but wanted to learn how to do it in c++ and this tutorial was perfect! Easy to understand and gave me the fundamentals to do what I want.
Ah, I wish you had done the presentation using a UNIX environment but nonetheless the explanation was superb and it was very useful for me. Thanks and bless you.
Thank you for hosting all your lectures. Your lessons are very awesome. I think using: using namespace std Is in general not good because of namespace cluttering Thank you so much for your lessons!! truly appreciated.
@@d4sty.Most of the time it’ll be ipv4… You can also edit it so it can look for which ever protocol version the client uses, then connects to the one it finds. But it’ll usually be ipv4
Thank you for sharing this very good lecture! One question please, @37:40 don't we need the shutdown() function before calling the WSACleanup() and before calling the closesocket()?
Thank you for making this video. Is there any way you can link the project files in the description? I also have maybe a somewhat naive question, but since we are using windocks, I'm assuming it's meant for windows. Will this also be compatible with linux-based Operating systems? Have a great day!
Hi there, yes, I have managed to code this on a Mac too (and confident it would be similar for Linux). The functions such as socket(), bind(), listen(), connect(), accept(), send(), recv() etc are the same for both Windows and Mac. Main differences are the low level Windows types (such as DWORD) are substituted for strings and integers with Mac. And rather than libraries winsock2.h and ws2tcpip.h, there are equivalent libraries such as arpa/inet.h, netdb.h, sys/socket.h, sys/types.h and unistd.h for Mac solutions.
@@NicholasDayPhD Hi Thank you very much for the detailed lectures. Would you please help me providing the info on how can we implement these in mac. Because we need two processes server and client, can we achieve this in mac terminal or do we need any IDE?
@@raghuvaranpothuganti I've managed to run similar code via the IDE Visual Studio Code (to compile the source C++ code in to an executable application). You can also get Visual Studio for Mac, or you may even prefer the IDE CLion by JetBrains (same developers of IntelliJ). Basically, you just need an IDE to compile the source code! Once compiled, clicking on the application will launch a terminal window. For this basic example, I had two terminal windows on the the same Mac (one for server, one for client). However, you could configure the applications to talk to each other across a network. Hope that helps...
Hi Mr. Day, I have encountered an error on codeblocks, and I have included all the supporting files u mentioned but compiler says, "InePton was not declared....." Could you please get me through this..
Putting "#define _WIN32_WINNT _WIN32_WINNT_VISTA" before "#include " and "#include " worked for me. This means Windows Vista is the oldest OS your code will work on though.
@@ShirChoi this series gives u a good outlook of what socketprogramming is. However, it doesn't work on codeblocks. I would recommend ruclips.net/p/PLhnN2F9NiVmAMn9iGB_Rtjs3aGef3GpSm&feature=shared
I know that this comment is 1 year old but this solution if for others to also see fix that worked for me : 1) include 2) in the place of the string _T("127.0.0.1") replace it with L"127.0.0.1"
Hi there - the notes for this course are based on Lippman's book on C++. Here is a simplified tutorial that may help: www.geeksforgeeks.org/socket-programming-cc/
Why do we even need to close them? Microsoft documentation says that all open sockets are automatically reset and deallocated once WSACleanup() is called.
Another source code tutorial I found uses int LISTENONPORT(int portno) as its entry point. Why, and why does this source code seem to loath my existance lol? Python is just like "Do socket stuff on X socket" and it just goes.
Because that's stupid. "Diving right in" just encourages people to type over and barely learn anything. It's important to understand the concepts you're going to implement before actually implementing them.
Does someone know where I can find the files "stdafx.h" and "targetver.h" ? I found them on Github but my IDE can't find the files afxwin.h, afxext.h, etc. Thanks for helping me...
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
This series alone is worth more than a bunch of paid Udemy courses. Thank you Nicholas for sharing your knowledge!
Yeah, for sure. This guy deserves millions
and a 100 videos playlist, just wrapped in 13 videos
this is pure gold. Havent watched to the end yet but it gives a lot of understanding on the subject in c++
Socket is a tricky issue and you explained It very well. Thank you for your pronunciation that sounds perfect to an italian native speaker.
Glad it was helpful!
Incredible. Half an hour in and the content is pure quality. Thank you sincerely!
Thank you so much - so glad this helped you!
Oh, my god. This channel deserves infinitely more suscriptors. Perfectly well explained such a difficult topic!
Thank you so much for this!
For anyone wondering, AF_INET is for IPv4 type addresses not TCP or UDP. AF_INET6 is used for IPv6 addresses. Only the _type_ parameter of the socket function is responsible for determining if it will be TCP or UDP.
After 2hours typing all the code in manually, it worked :)
Hello can you help me out in understanding socket
Great video! I have previously done work with sockets in python but wanted to learn how to do it in c++ and this tutorial was perfect! Easy to understand and gave me the fundamentals to do what I want.
Same!
This series is seriously underrated for such a high quality explanation!
Thank you so much - glad this material helps you!
Waiting for part 2! It's such a great video tbh. Best one about this topic
Thanks bro, clean voice, clean code❤
Ah, I wish you had done the presentation using a UNIX environment but nonetheless the explanation was superb and it was very useful for me. Thanks and bless you.
Thanks so much - it's not too difficult to get this working in a UNIX environment. The functions should be the same!
Thank you for hosting all your lectures. Your lessons are very awesome.
I think using: using namespace std
Is in general not good because of namespace cluttering
Thank you so much for your lessons!! truly appreciated.
Very kind of you to write this feedback - noted for future!
but it's cleaner and it doesn't cause problems usually
this was super entertaining and informative, even though it's in a language i don't use. subscribed
This is gold for me. Thank you
You're very welcome!
Seems interesting. Fortunately I want to implement networking for my games and engine in a short future
37:00 af_inet refers to ipv4, not tcp or udp.
af_inet6 refers to ipv6.
so how do i know if the client uses ipv6 or ipv4??? does it still connect you if you are on a different one?
@@d4sty.Most of the time it’ll be ipv4… You can also edit it so it can look for which ever protocol version the client uses, then connects to the one it finds. But it’ll usually be ipv4
Hello sir, I was wondering how you added the two header files(stdafx.h & targetver.h)? I cant seem to figure it out on visual studio 2019
Did you add them ? if yes, how please
Can you please share the document reference you are using in the video?
awesome lecture
Where can I download the stdafx.h header file????
hello i was wondering about where i can find that word document where is all the step by step plss
Thank you for sharing this very good lecture!
One question please, @37:40 don't we need the shutdown() function before calling the WSACleanup() and before calling the closesocket()?
Can anyone tell this lecture is for windows ?
"InetPton" was not declared in this scope. Got all the headers, libraries, everything.
thank you, could you take another video in c#, I very need it.
Hello, I would like to ask if other computer can connect to that server and send binary text?
1:01:53 How do i do this on different Machines?
Thank you so much for these videos!! But I do not know where can I find your word document. 😭
Crystal clear, thank you so much🙏
Nice!
I love you dude
love it tysm
Thank you for making this video. Is there any way you can link the project files in the description? I also have maybe a somewhat naive question, but since we are using windocks, I'm assuming it's meant for windows. Will this also be compatible with linux-based Operating systems? Have a great day!
Hi there, yes, I have managed to code this on a Mac too (and confident it would be similar for Linux). The functions such as socket(), bind(), listen(), connect(), accept(), send(), recv() etc are the same for both Windows and Mac. Main differences are the low level Windows types (such as DWORD) are substituted for strings and integers with Mac. And rather than libraries winsock2.h and ws2tcpip.h, there are equivalent libraries such as arpa/inet.h, netdb.h, sys/socket.h, sys/types.h and unistd.h for Mac solutions.
@@NicholasDayPhD Hi Thank you very much for the detailed lectures. Would you please help me providing the info on how can we implement these in mac. Because we need two processes server and client, can we achieve this in mac terminal or do we need any IDE?
@@raghuvaranpothuganti I've managed to run similar code via the IDE Visual Studio Code (to compile the source C++ code in to an executable application). You can also get Visual Studio for Mac, or you may even prefer the IDE CLion by JetBrains (same developers of IntelliJ). Basically, you just need an IDE to compile the source code! Once compiled, clicking on the application will launch a terminal window. For this basic example, I had two terminal windows on the the same Mac (one for server, one for client). However, you could configure the applications to talk to each other across a network. Hope that helps...
@@NicholasDayPhD i guess you don't need the initialize WSA part, in linux based systems right ?
Hi Mr. Day, I have encountered an error on codeblocks, and I have included all the supporting files u mentioned but compiler says, "InePton was not declared....." Could you please get me through this..
Putting "#define _WIN32_WINNT _WIN32_WINNT_VISTA" before "#include " and "#include " worked for me. This means Windows Vista is the oldest OS your code will work on though.
Did you find the answer for you question? I am facing the same problem rn and can't find the answer
@@ShirChoi this series gives u a good outlook of what socketprogramming is. However, it doesn't work on codeblocks. I would recommend ruclips.net/p/PLhnN2F9NiVmAMn9iGB_Rtjs3aGef3GpSm&feature=shared
I know that this comment is 1 year old but this solution if for others to also see
fix that worked for me :
1) include
2) in the place of the string _T("127.0.0.1")
replace it with L"127.0.0.1"
Where can we find notes sir ?
Hi there - the notes for this course are based on Lippman's book on C++. Here is a simplified tutorial that may help: www.geeksforgeeks.org/socket-programming-cc/
why would you make it white its so bright my developer eyes cant handle this
I assume that this would be similar to network programming with C++ in Linux
No.
No. This isn't even C++, it's the Windows API.
Why aren't we calling closesocket() when acceptSocket fails?
f
Why do we even need to close them? Microsoft documentation says that all open sockets are automatically reset and deallocated once WSACleanup() is called.
very great
Thanks a lot
pure goldmine
well explained please can you send me PPT lectures
please share word document
Another source code tutorial I found uses int LISTENONPORT(int portno) as its entry point. Why, and why does this source code seem to loath my existance lol? Python is just like "Do socket stuff on X socket" and it just goes.
👏👏🙏
uhm, i don't know.
i am a person who don't like long video ;-;
Networking programming in windows is fake
Why don't you just dive right in? Some of us hate "theory" just explain things while you code! Otherwise great video!
Because that's stupid. "Diving right in" just encourages people to type over and barely learn anything. It's important to understand the concepts you're going to implement before actually implementing them.
he included timestamps so people who dont wanna learn theory can skip it, why are you being bitchy for no reason?
really like your c++ series! I would like to know where can I get stdafx.h and targetver.h files.
Thank you so much! You can find them with older C++ projects. Should be freely available on the internet.
Hey, where can I find the word document?
Does someone know where I can find the files "stdafx.h" and "targetver.h" ? I found them on Github but my IDE can't find the files afxwin.h, afxext.h, etc. Thanks for helping me...
you don't need any of those you can run your programs without those