- Est-ce que le serveur doit ensuite fermer ce socket et en ouvrir un à chaque fois qu'un client fait une requète ou est-ce que c'est une fois au départ et on la garde dans que le client n'a pas finit ou un certain temps ?  

- Le serveur doit stocker les sockets créé mais comment fait-il pour écouter les demandes de connexions et répondre aux client déjà connectés?  

- Je devrais utiliser les threads. Vois pas concrètement à quoi ils servent.  
- On m'a dit que je devrais utiliser le mode asynchrone parce que j'aurais bcp de socket mais comment ça marche (je crois que c'est pour ne pas bloquer le serveur sur un client mais je comprend même pas bien pourquoi il se bloquerais ?)  

comprend pas, désolé  

Qu'est-ce  que change l'asynchrone dans mon algo, je vois pas?(enfin je dois pas comprendre quoi!)

The Windows Sockets select function determines the status of one or more sockets, waiting if necessary, to perform synchronous I/O.
 
int select (
  int nfds,                            
  fd_set FAR * readfds,                
  fd_set FAR * writefds,              
  fd_set FAR * exceptfds,              
  const struct timeval FAR * timeout  
);
 
Parameters
nfds  
[in] This parameter is ignored; it is included only for compatibility with Berkeley sockets.  
readfds  
[in/out] An optional pointer to a set of sockets to be checked for readability.  
writefds  
[in/out] An optional pointer to a set of sockets to be checked for writability  
exceptfds  
[in/out] An optional pointer to a set of sockets to be checked for errors.  
timeout  
[in] The maximum time for select to wait, or NULL for blocking operation.  
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 out-of-band 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 writable 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 out-of-band data (see section DECnet Out-Of-band data for a discussion of this topic) or any exceptional error conditions.  
 
Important Out-of-band 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 timeout controls how long the select can take to complete. If timeout is a null pointer, select will block indefinitely until at least one descriptor meets the specified criteria. Otherwise, timeout 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.
 
Return Values
The select function returns the total number of socket handles that are ready and contained in the FD_SET structures, zero if the time limit expired, or SOCKET_ERROR if an error occurred. If the return value is SOCKET_ERROR, WSAGetLastError can be used to retrieve a specific error code.
 
Error Codes
WSANOTINITIALISED A successful WSAStartup must occur before using this function.  
WSAEFAULT The Windows Sockets implementation was unable to allocate needed resources for its internal operations, or the readfds, writefds, exceptfds, or timeval parameters are not part of the user address space.  
WSAENETDOWN The network subsystem has failed.  
WSAEINVAL The timeout value is not valid, or all three descriptor parameters were NULL.  
WSAEINTR A blocking Windows Socket 1.1 call was canceled through WSACancelBlockingCall.  
WSAEINPROGRESS A blocking Windows Sockets 1.1 call is in progress, or the service provider is still processing a callback function.  
WSAENOTSOCK One of the descriptor sets contains an entry that is not a socket.  
 
 
QuickInfo
  Windows NT: Yes
  Windows: Yes
  Windows CE: Use version 1.0 and later.
  Header: Declared in winsock2.h.
  Import Library: Link with ws2_32.lib.
 
See Also
accept, connect, recv, recvfrom, send, WSAAsyncSelect, WSAEventSelect