Where is winsock library

I have some errors when linking because, in my opinion, the library winsock. I found out how to do it: rpath specifies where the provided libraries are located. Edit: To answer the question in the comment below " Is there any way to use nvcc to turn mylib. Rajat Gupta. Only authorized users can answer the question. Please sign in first, or register a free account. Finally, the lpVendorInfo field is reserved for vendor-specific information regarding the implementation of Winsock.

This field is not used on any Windows platforms. For the most part, when writing new applications you will load the latest version of the Winsock library currently available.

Remember that if, for example, Winsock 3 is released, your application that loads version 2. When your application is completely finished using the Winsock interface, you should call WSACleanup , which allows Winsock to free up any resources allocated by Winsock and cancel any pending Winsock calls that your application made. Replies: 3 Last Post: , AM. Replies: 13 Last Post: , PM.

Where do I initialize Winsock and catch messages for it? By Lithorien in forum Windows Programming. Replies: 10 Last Post: , PM. Replies: 4 Last Post: , AM. Now run the program in 1 terminal , and open 3 other terminals. From each of the 3 terminal do a telnet to the server port. At the telnet shell, run the command "open localhost ". This command will try to connect to localhost on port number Next you should see the following message at the telnet prompt.

This message is received from the socket server running on port On the other hand, the server terminal would show the following messages, indicating that a client connected to it.

So now the server is running nonstop and the telnet terminals are also connected nonstop. Now close the server program. All telnet terminals would show "Connection to host lost. But still there is not effective communication between the server and the client.

The server program accepts connections in a loop and just send them a reply, after that it does nothing with them. Also it is not able to handle more than 1 connection at a time.

So now its time to handle the connections , and handle multiple connections together. To handle every connection we need a separate handling code to run along with the main server accepting connections. One way to achieve this is using threads. The main server program accepts a connection and creates a new thread to handle communication for the connection, and then the server goes back to accept more connections.

We shall now use threads to create handlers for each connection the server accepts. Lets do it pal. Run the above server and open 3 terminals like before. Now the server will create a thread for each client connecting to it.

This one looks good , but the communication handler is also quite dumb. After the greeting it terminates. It should stay alive and keep communicating with the client. One way to do this is by making the connection handler wait for some message from a client as long as the client is connected.

If the client disconnects , the connection handler ends. The above connection handler takes some input from the client and replies back with the same. Here is how the telnet output might look. The winsock api is quite similar to Linux sockets in terms of function name and structures. Few differences exist like :.

Header file names are different. Winsock needs winsock2. Winsock function to close a socket is closesocket , whereas on Linux it is close. On Linux the errno variable from errno. By now you must have learned the basics of socket programming in C. You can try out some experiments like writing a chat client or something similar.

If you think that the tutorial needs some addons or improvements or any of the code snippets above dont work then feel free to make a comment below so that it gets fixed. He can be reached at [email protected]. Hey Silver Moon, Thank you very much for sharing your codes and the introduction — keep going :-! Good and newbie-friendly tutorial. Your examples are hard to follow.

For crying out loud all you are doing is creating a socket, connecting to server and sending info. Also, the client application has an outdated inet address for google. Without generating income from this site, the user is under no obligation to update the content presented.

Go elsewhere if it is not satisfactory. That falls down to coder preference. Their is no particularly wrong answer. 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. I had to ping Google. And you found the solution yourself. In summation: Quit whining. This is C code. If you wanted something soft and easy, try Python or Javascript.