about select()

来源：互联网发布：windows 用户界面设计编辑：程序博客网时间：2024/06/05 10:39

usages of select

a) test the socket status

b) Set interval time, a way of timeout control.

Prototype:

int select(
  int nfds,                           
  fd_set FAR *readfds,               
  fd_set FAR *writefds,              
  fd_set FAR *exceptfds,             
  const struct timeval FAR *timeout  
);

Notes:

·the fd_set need have at least one component, or the select() would return WSAEINVAL.

·return zero if the time limit expired.

·ignore the first parameter.

***when select() is called, you need to re-initial the fd_set.

How to use:

we may use this function to implement timeout control of blocking socket functions as send(), recv() and accept(). Just follow the steps:

i. Setup a fd_set struct, input the watching socket

ii. set a time interval

iii. select()

iv. switch the return value

Example: select() Timeout control in blocking mode socket.

//Timeout control in blocking mode with select().

//returns the total number sent, zero for the time limit expired, SOCKET_ERROR for an error.

DWORD WriteComm(const LPBYTE lpBuffer, DWORD dwCount, DWORD dwTimeout)

{

fd_set fdWrite = { 0 };

TIMEVAL stTime;

TIMEVAL *pstTime = NULL;

if ( INFINITE != dwTimeout ) {

stTime.tv_sec = dwTimeout/1000;

stTime.tv_usec = dwTimeout % 1000;

pstTime = &stTime;

}

// Set Descriptor

if ( !FD_ISSET( s, &fdWrite ) )

FD_SET( s, &fdWrite );

// Select function set write timeout

DWORD dwBytesWritten = 0L;

// timeout parameter NULL for blocking operation.

int res = select( s+1, NULL, &fdWrite, NULL, pstTime );

if (res > 0) {

res = send( s, (LPCSTR)lpBuffer, dwCount, 0);//won't return zero

dwBytesWritten = (DWORD)((res >= 0)?(res) : (SOCKET_ERROR));

}

return dwBytesWritten;

}

If wanna watch the accept fun, just use the codes:

int res = select(sock+1, &fdRead, NULL, NULL, pstTime);

if (res <= 0)

sock = INVALID_SOCKET;

else

sock = accept(sock, 0, 0);

from the MSDN:

Remarks

The select function is used to determine the status of one or more sockets. For each socket, the caller can request information on read, write, or error status. The set of sockets for which a given status is requested is indicated by an fd_set structure. The sockets contained within the fd_set structures must be associated with a single service provider. For the purpose of this restriction, sockets are considered to be from the same service provider if the WSAPROTOCOL_INFO structures describing their protocols have the same providerId value. Upon return, the structures are updated to reflect the subset of these sockets that meet the specified condition. The select function returns the number of sockets meeting the conditions. A set of macros is provided for manipulating an fd_set structure. These macros are compatible with those used in the Berkeley software, but the underlying representation is completely different.

The parameter readfds identifies the sockets that are to be checked for readability. If the socket is currently in the listen state, it will be marked as readable if an incoming connection request has been received such that an accept is guaranteed to complete without blocking. For other sockets, readability means that queued data is available for reading such that a call to recv, WSARecv, WSARecvFrom, or recvfrom is guaranteed not to block.

For connection-oriented sockets, readability can also indicate that a request to close the socket has been received from the peer. If the virtual circuit was closed gracefully, and all data was received, then a recv will return immediately with zero bytes read. If the virtual circuit was reset, then a recv will complete immediately with an error code such as WSAECONNRESET. The presence of OOB data will be checked if the socket option SO_OOBINLINE has been enabled (see setsockopt).

The parameter writefds identifies the sockets that are to be checked for writability. If a socket is processing a connect call (nonblocking), a socket is writeable if the connection establishment successfully completes. If the socket is not processing a connect call, writability means a send, sendto, or WSASendto are guaranteed to succeed. However, they can block on a blocking socket if the len parameter exceeds the amount of outgoing system buffer space available. It is not specified how long these guarantees can be assumed to be valid, particularly in a multithreaded environment.

The parameter exceptfds identifies the sockets that are to be checked for the presence of OOB data (see section DECnet Out-of-band data for a discussion of this topic) or any exceptional error conditions.

Important OOB data will only be reported in this way if the option SO_OOBINLINE is FALSE. If a socket is processing a connect call (nonblocking), failure of the connect attempt is indicated in exceptfds (application must then call getsockopt SO_ERROR to determine the error value to describe why the failure occurred). This document does not define which other errors will be included.

Any two of the parameters, readfds, writefds, or exceptfds, can be given as NULL. At least one must be non-NULL, and any non-NULL descriptor set must contain at least one handle to a socket.

Summary: A socket will be identified in a particular set when select returns if:

readfds:

If listen has been called and a connection is pending, accept will succeed.
Data is available for reading (includes OOB data if SO_OOBINLINE is enabled).
Connection has been closed/reset/terminated.

writefds:

If processing a connect call (nonblocking), connection has succeeded.
Data can be sent.

exceptfds:

If processing a connect call (nonblocking), connection attempt failed.
OOB data is available for reading (only if SO_OOBINLINE is disabled).

Four macros are defined in the header file Winsock2.h for manipulating and checking the descriptor sets. The variable FD_SETSIZE determines the maximum number of descriptors in a set. (The default value of FD_SETSIZE is 64, which can be modified by defining FD_SETSIZE to another value before including Winsock2.h.) Internally, socket handles in an fd_set structure are not represented as bit flags as in Berkeley Unix. Their data representation is opaque. Use of these macros will maintain software portability between different socket environments. The macros to manipulate and check fd_set contents are:

FD_CLR(s, *set)

Removes the descriptor s from set.

FD_ISSET(s, *set)

Nonzero if s is a member of the set. Otherwise, zero.

FD_SET(s, *set)

Adds descriptor s to set.

FD_ZERO(*set)

Initializes the set to the NULL set.

The parameter time-out controls how long the select can take to complete. If time-out is a NULL pointer, select will block indefinitely until at least one descriptor meets the specified criteria. Otherwise, time-out points to a TIMEVAL structure that specifies the maximum time that select should wait before returning. When select returns, the contents of the TIMEVAL structure are not altered. If TIMEVAL is initialized to {0, 0}, select will return immediately; this is used to poll the state of the selected sockets. If select returns immediately, then the select call is considered nonblocking and the standard assumptions for nonblocking calls apply. For example, the blocking hook will not be called, and Windows Sockets will not yield.

Note The select function has no effect on the persistence of socket events registered with WSAAsyncSelect or WSAEventSelect.