Hi bkelly13 ! The "WSASocket API" are Microsoft-specific new functions for handling sockets in Windows. If your code is to run on Windows machines only go with this new API since it provides more flexibility and some functionality benefits when working with types of sockets other than blocking. Here are some qoutes from the Remarks paragraph in the MSDN regarding WSARecv
:
Quote:
The WSARecv function provides some additional features compared with the standard recv function in three important areas: •It can be used in conjunction with overlapped sockets to perform overlapped recv operations. •It allows multiple receive buffers to be specified making it applicable to the scatter/gather type of I/O. •The lpFlags parameter is used both on input and returned on output, allowing applications to sense the output state of the MSG_PARTIAL flag bit. However, the MSG_PARTIAL flag bit is not supported by all protocols.
Same goes for WSASend
:
Quote:
The WSASend function provides functionality over and above the standard send function in two important areas: •It can be used in conjunction with overlapped sockets to perform overlapped send operations. •It allows multiple send buffers to be specified making it applicable to the scatter/gather type of I/O.
You can also find code examples for working with these API in there. I have created and worked with sockets using this API (Blocking mode and event-based Overlapped mode) and overall it seems to work fine. If relevant, I can send you the code. :cool: Bye, Amit C.