Deviation from Berkeley Sockets

There are a few limited instances where the Windows Sockets API has had to divert from strict adherence to the Berkeley conventions, usually because of difficulties of implementation in a Windows environment.

socket data type and error values

select() and FD_*

Error codes -- errno, h_errno & WSAGetLastError()

Pointers

Renamed functions

Blocking routines & EINPROGRESS

Maximum number of sockets supported

Include files

Return values on API failure