Validity of a Socket
I have created a socket using the following lines of code and i get a valid socket and connection is established between the client and server machines. Is there a possibility that the socket becomes invalid due to network disturbances or any other reason.
If so how do we check whether the socket is valid or not.
SOCKET SocServer;
//To Set up the sockaddr structure
ServerSock.sin_family = AF_INET;
ServerSock.sin_addr.s_addr = INADDR_ANY
ServerSock.sin_port = htons(PortNumber);//port number of 5005开发者_如何学运维
// To Create a socket for listening on PortNumber
if(( SocServer = socket( AF_INET, SOCK_STREAM, 0 )) == INVALID_SOCKET )
{
return FALSE;
}
//To bind the socket with wPortNumber
if(bind(SocServer,(sockaddr*)&ServerSock,sizeof(ServerSock))!=0)
{
return FALSE;
}
// To Listen for the connection on wPortNumber
if(listen(SocServer,SOMAXCONN)!=0)
{
return FALSE;
}
I know i can check for INVALID_SOCKET which in other words means the socket is 0. Is there any other way out because my SocServer will have a value say 2500, i want to check if this socket is valid.
Pass your socket to any one of the windows socket functions (eg. getsockopt()
), if the socket is invalid, it will return SOCKET_ERROR
while WSAGetLastError()
will return WSAENOTSOCK
.
It is important to note that INVALID_SOCKET
does not equal 0
(the actual value, which you should not use specifically is ((SOCKET)(~0))
The socket can become "invalid" when either side (expected or unexpected) disconnects, but not out of the blue due to network interferences (unless it disconnects, read above).
You can detect this by checking the return values of send()
and recv()
for -1 (SOCKET_ERROR)
The socket will not go invalid. But after you listen() you must accept() a connection. That connection may be lost at some point. It could be detected by a failure to write to the socket or recv() returning with error. Then you just recycle back to listen().
First, assuming that INVALID_SOCKET (which you don't show) is actually defined as 0 this is incorrect. socket
returns -1 on failure like the other system calls (0 is a valid fd that could be returned).
Then once you accept a connection, your send
/write
or recv
/read
call will return -1. If you're trying to write, errno
will be set to EPIPE
to indicate the socket was closed (by your client). There's no way to just ask if a socket is closed.
精彩评论