Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Porting Socket Applications to Winsock

This section describes Winsock porting considerations.

There are a limited number of instances where Windows Sockets has diverted from strict adherence to the Berkeley conventions, usually due to implementation difficulties in the Microsoft Windows environment.

When a deviation from Berkeley conventions occurs in Windows Sockets, the deviation is specifically and clearly noted. For example, if a function is specific to Windows Sockets, that deviation is specified with a phrase in the function description similar to the following:

The [function-name] function is a Microsoft-specific extension to the Windows Sockets 2 API.

This section provides information about porting Berkeley (BSD) UNIX socket applications to Winsock:

Related topics

Handling Winsock Errors
Porting Socket Applications to Winsock
Windows Sockets Error Codes
Winsock Programming Considerations



Community Additions

© 2015 Microsoft