WSAEventSelect与accept触发的问题??

[aneird]

初始化socket;
位置1.saccept =accept(sockList[eventIndex],NULL,NULL);
int rc = WSAEventSelect(sock, eventList,FD_READ|FD_WRITE|FD_ACCEPT|FD_CLOSE|FD_CONNECT);
位置2.saccept =accept(sockList[eventIndex],NULL,NULL);
为什么放在位置1时程序就阻塞在那了，放在位置2时就不阻塞了(没有客户端连接)，就是给sock注册消息的问题，谁能具体讲一下WSAEventSelect是怎么回事 不就是给他sock注册事件吗，我认识位置2页也应该阻塞在那，即使给他注册事件了，因为没有客户端连接啊。请同志们解释解释。。。。。。

[aneird]

????????

[科学家]

WSAEventSelect(sock, eventList,FD_READ|FD_WRITE|FD_ACCEPT|FD_CLOSE|FD_CONNECT);
的意思是：如果sock发生了FD_READ|FD_WRITE|FD_ACCEPT|FD_CLOSE|FD_CONNECT之一的事件，就触发eventList事件。

[lanhanNO_1]

Select是个查询过程
没有用sockList[eventIndex]
accept使用

[aneird]

?

[lanhanNO_1]

看了第一个位置不用说了
int rc = WSAEventSelect(sock, eventList,FD_READ|FD_WRITE|FD_ACCEPT|FD_CLOSE|FD_CONNECT);
执行后返回个WSAENOTSOCK 什么状态都一样 不知道和环境有没有关系
saccept =accept(sockList[eventIndex],NULL,NULL);
就直接返回个0

Data arrives on socket s; Windows Sockets sets the WSAEventSelect event object.
The application does some other processing.
While processing, the application issues an ioctlsocket(s, FIONREAD...) and notices that there is data ready to be read.
The application issues a recv(s,...) to read the data.
The application eventually waits on the event object specified in WSAEventSelect, which returns immediately indicating that data is ready to read.
The application issues recv(s,...), which fails with the error WSAEWOULDBLOCK.
全鸟语看不懂 关注中