you are criticizing someone who is putting out information for free.

Also, it is not their fault that you are terrible at programming. Wait tell you have to get this information together YOURSELF from the microsoft docs or (worse yet for someone like you) a goddamn book.

you are right, new_socket should also be closed if its a valid socket.
i missed that!

Why you only close socket “s” and not “new_socket” ?

yes, this code has been tested to run in visual studio c++
create project, add source code file and compile.

gcc .\server_main.cpp -o server -lws2_32

type this while compliling

A note:
in the chapter “Handling Connections” no sample source code and no output in the boxes is shown.

See comments:

Why don’t you update all you typos? The HTML versions of (“,) Take about 30 minutes to edit. It’s a pain to have to edit this code. If not just take this site down, it’s not worth trying to figure this all out. (Without generating income from this site, the user is under no obligation to update the content presented. Go elsewhere if it is not satisfactory.)

Then you use ‘s’ as a variable for ‘socket’, why not use something more descriptive such as sock_p , for primary socket. Your examples are hard to follow. (That falls down to coder preference. I used “sock” some prefer “s”. Their is no particularly wrong answer.)

For crying out loud all you are doing is creating a socket, connecting to server and sending info. If your variables were more discriptive it wouldn’t took take two days to debug your code to getting running for the absolute beginer. (In C code, that is quite the accomplishment. Especially on a windows machine. As for the debugging, that is a natural part of coding and most of your time will be spent doing it.)

Also, the client application has an outdated inet address for google. It doesn’t connect and it took me two days to figure that out, since I have zero previous knowledge of Socket programing. (Great! You just learned the first rule of using other people’s code: trust nothing.)

I had to ping Google.com to get a current Inet Address. (And you found the solution yourself. I’d bet fifty bucks that you won’t be making this mistake again.)

In summation: Quit whining. This is C code. If you wanted something soft and easy, try Python or Javascript. As for the time-consuming nature of code debugging, that is a natural part of coding. Coding is 90% debugging, 5% grunt work, 4% comprehension, and 1% coke-fueled, near-psychedelic, code creation. It’s that 1% part that I keep coming back for. There is no high better than a coder’s. And I have yet to find something more enjoyable than a perfectly executed piece of code.

Then you use ‘s’ as a variable for ‘socket’, why not use something more descriptive such as sock_p , for primary socket. Your examples are hard to follow.

For crying out loud all you are doing is creating a socket, connecting to server and sending info. If your variables were more discriptive it wouldn’t took take two days to debug your code to getting running for the absolute beginer.

Also, the client application has an outdated inet address for google. It doesn’t connect and it took me two days to figure that out, since I have zero previous knowledge of Socket programing.

I had to ping Google.com to get a current Inet Address.

Sure, use 127.0.0.1 address

lol
they copied my article.

Hey, were you able to find the last two codes ?
Regards
Sumit