The information in this section is included for DirectPlayLobby client developers, and contains information that, in general, is not relevant for application developers.
DirectPlay can encapsulate network address data. DirectPlay contains all the information needed to connect to a DirectPlay session. The purpose of this information is to be able to connect an application to a session without the service provider having to display any dialog boxes prompting the user for information. By providing the service provider with a complete DirectPlay Address, an application can bypass the dialog boxes that the service provider would typically display to obtain this information from the user.
The DirectPlay Address is in a format similar to the Resource Interchange File Format (RIFF). It is composed of a series of chunks. Each chunk consists of the following:
·A globally unique identifier (GUID) indicating what type of data this chunk contains
·The size of the data
·The data field
DirectPlay has predefined the following chunk identifiers:
GUID Type of data
DPAID_ComPort A DPCOMPORTADDRESS structure that specifies:
·COM port to use (1-4)
·Baud (100-256k)
·Number of stop bits (1-2)
·Parity (0-none, 1-odd, 2-even, 3-mark)
·Flow control (0-none, 1-xon/xoff, 2-RTS, 3-DTR, 4-RTS/DTR)
DPAID_Inet ASCII string representing an IP address of the form "xxx.xxx.xxx.xxx" or a server name, such as "dplay.microsoft.com".
DPAID_Phone ASCII string representing the numeric digits of a phone number.
DPAID_ServiceProvider A 16-byte GUID of the service provider for which this address was created. This chunk can be ignored because several different service providers can use the same type of network address.
A chunk identifier is a 16-byte GUID.