The Windows Sockets API interface provided by this system (winking) is a function (routine) as defined in version 1.1 of WINSOCK (as appendix) published on January 20, 1993; includes 30 Berkeley Software Dis Tribution (BSD) function and 16 functions that conform to the Windows message-driven feature.
The BSD functions include:
Accept () bind () closesocket () Connect ()
Getpeername () getsockname () getsockopt () htonl ()
Htons () inet_addr () Inet_ntoa () ioctlsocket ()
Listen () Ntohl () Ntohs () recv ()
Recvfrom () Select () Send () sendto ()
SetSockOpt () shutdown () socket () GetHostName ()
GETHOSTBYADDR () gethostbyname ()
Getprotobyname () Getprotobynumber ()
Getservbyname () Getservbyport ()
The Microsoft windows-specific Extensions functions include:
WSAASYNCGETHOSTBYADDR () WSAAsyncGetHostByName ()
Wsaasyncgetprotobyname () Wsaasyncgetprotobynumber ()
Wsaasyncgetservbyname () Wsaasyncgetservbyport ()
WSAAsyncSelect () wsacancelasyncrequest ()
WSACancelBlockingCall () WSACleanup ()
WSAGetLastError () wsaisblocking ()
Wsasetblockinghook () Wsasetlasterror ()
WSAStartup () Wsaunhookblockinghook ()
These API interfaces apply to the Internet Protocol Suite (IPS, commonly referred to as TCP/IP),
Support Stream (TCP) and Datagram (UDP) sockets.
Stream (TCP) sockets provide "two-way", "reliable", "orderly", "not repeated" data transfer.
Datagram (UDP) sockets provide "two-way" communication, but there is no "reliable", "orderly", "no repeat" and so on, so users may receive the information is not ordered, repeated, and even the data may be missing in the transmission process.