who could help me for error number 10035

I write server and client,and linking using SOCK_STREAM.at server I send a file
and at client I receive it,and at client I use:
WSAAsyncSelect(m_socket,m_hWnd,WM_SOCK,FD_READ);
and look:

Code:

void CChatCDlg::OnSock(WPARAM wParam,LPARAM lParam)
{
	switch(LOWORD(lParam))
	{
	case FD_READ:
			wlength = recv(m_socket,buffer,8000,0);
			if(SOCKET_ERROR == wlength) 
			{ 
                             int err=WSAGetLastError();
			      CString str;
			      str.Format("Error number:%d",err);
                              AfxMessageBox(str);  
			      return; 
			} 
		break;
	}
}

I get the error number is 10035,I want to know how to correct?

The error message you are getting is WSAWOULDBLOCK, basically indicating that recv is in non-blocking mode and there is no data, so it would block and wait for data if the call proceeded. It's also possible from the error description that your connection has not stabilized and might cause errors if recv continued.

Windows Sockets Error Codes (Windows) (When in doubt... look it up!)

So... are you using non-blocking sockets?

I use WSAAsyncSelect(m_socket,m_hWnd,WM_SOCK,FD_READ);
how to correct it?

Are you intending to use blocking sockets? I would guess "no", just based on the word "chat" in the original code.

To "fix it", you need to wait until the person on the other end says something, or better yet, do whatever is the WSA equivalent of select to check whether there is data waiting.

Originally Posted by tabstop

Are you intending to use blocking sockets? I would guess "no", just based on the word "chat" in the original code.

To "fix it", you need to wait until the person on the other end says something, or better yet, do whatever is the WSA equivalent of select to check whether there is data waiting.

select function (Windows)

Calling select() with the right setups will tell him which sockets have pending data... from there he can call recv().

WSAAsyncSelect() is a way of setting up window messages so that he gets notification in his message loop whenever a socket event occurs... It's not wrong, but it's really intended to work with blocking sockets... The idea is that when you get a message notifying you of a pending message you call recv() or recvfrom()...

http://msdn.microsoft.com/en-us/libr...40(VS.85).aspx

Overall it would be simpler to set up a separate thread to handle and display received messages, using blocking sockets. It could just sit there in recv() waiting for a message then when recv() unblocks the thread could display the message in a windows control such as a listbox or edit on the user interface and then go right back to receiving.