See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
A version of this page is also available for
4/8/2010
A service provider should treat all sockaddrcalls exclusive of the address family parameter as if they are in the network byte order, and the address family parameter as in the local machine's byte order. It is the Winsock application's responsibility to make sure that addresses contained in sockaddrstructures are properly arranged. The Winsock API provides a number of conversion routines to simplify this task. Currently these routines understand conversion between the local host's natural byte order and either big-endian or little-endian network byte ordering. The Winsock architecture can support other byte ordering schemes in the future.