WinSock2 questions - really simple READ ME!

BeanDog · 2000-06-26T06:44:26

OK, i''ve gone and done it, I''m going through that WinSock2 article. I''ve got a few questions where the article makes assumptions of user knowledge. Remember that I KNOW NOTHING!!! ahem. mainly, I''m interested in information regarding sockets. Now, in the tutorial, it tells you to make this and this and this socket, but doesn''t exactly explain what they do or how they work. For instance, if I do client[NumClients] = accept(s, clientaddr[NumClients], &addr_size); s is a socket on the server, right? Sockets reside on the individual computer, right? So s is a socket on the server, and clientaddr[NumClients] (a sockaddr type) is information regarding the client computer''s ip and such nonsense, correct? And when I do connect(mainsock, target, sizeof(target)); the mainsock is the socket on the client computer, correct? But a port is network-wide, right? So if I bind the server''s socket to, say, port 5001, all the clients would try to connect to 5001, right? So I only have to have one computer bind to a port, that way I don''t try to make 2 duplicate ports. What''s really confusing me is the accept(...) function. When I call it, I pass in a reference to a sockaddr to be filled, and it returns a SOCKET! But wait a sec, this ruins the whole purpose for binding to a port, right? Then the server has a socket to each of the clients and the clients each have exactly ONE socket to the server, correct? This is all fine and dandy, but what exactly does the port do now? Does it ever do anything except provide connections? I''ll come on later and ask more, but I''m tired and confused and I''ll probly go to bed soon anyhoo. Thanks for reading, ~BenDilts( void ); President, BDAA

Networking and Multiplayer Programming

Started by BeanDog June 20, 2000 09:23 PM

10 comments, last by BeanDog 24 years, 5 months ago

Claus Hansen Ries

122

June 24, 2000 05:12 PM

Dont you use the winsock documentation??, it does not return true or false. =)

---- READ ----
If no error occurs, connect returns zero. Otherwise, it returns SOCKET_ERROR, and a specific error code can be retrieved by calling WSAGetLastError.

On a blocking socket, the return value indicates success or failure of the connection attempt.

With a nonblocking socket, the connection attempt cannot be completed immediately. In this case, connect will return SOCKET_ERROR, and WSAGetLastError will return WSAEWOULDBLOCK.

Ries