Basic Approach for getXbyY in the SPI (Windows Embedded CE 6.0)

  • Article

1/6/2010

Most getXbyY functions are translated by Ws2.dll to a WSALookupServiceBegin, WSALookupServiceNext, WSALookupServiceEnd sequence that uses one of a set of special GUIDs as the service class. These GUIDs identify the type of getXbyY operation that is being emulated. The query is constrained to those NSPs that support AF_INET. Whenever a getXbyY function returns a hostent or servent structure, Ws2.dll will specify the LUP_RETURN_BLOB flag in WSALookupServiceBegin so that the desired information will be returned by the NSP. These structures must be modified slightly in that the pointers contained within must be replaced with offsets that are relative to the start of the binary large object (BLOB) data. All values referenced by these pointer members must, of course, be completely contained within the BLOB, and all strings are ASCII.

See Also

Concepts

Compatible Name Resolution for TCP/IP in the Windows Sockets 1.1 SPI