Requesting Transport-Specific Actions

The following figure shows how a TDI client can make transport-specific action requests to the underlying TDI driver if that transport defines such extensions to TDI.

A TDI client can send special or proprietary extension requests to a TDI transport driver that defines a set of transport-specific action codes for these operations. These extensions, which can concern an open address, an open connection endpoint, or an open control channel, apply only to the calling client and not to any other TDI transport clients or drivers.

To request such a transport-defined action operation, the client first must open the address, connection endpoint, or control channel, as already described in Opening a Transport Address, Opening a Connection Endpoint, or Setting and Querying Information, respectively. Then, the client can use TdiBuildActionto set up a TDI_ACTION request with a client-supplied buffer containing the transport-defined action code and corresponding action parameter block for the requested operation.

Note   The TDI feature is deprecated and will be removed in future versions of Microsoft Windows. Depending on how you use TDI, use either the Winsock Kernel (WSK) or Windows Filtering Platform (WFP). For more information about WFP and WSK, see Windows Filtering Platform and Winsock Kernel. For a Windows Core Networking blog entry about WSK and TDI, see Introduction to Winsock Kernel (WSK).

 

 

 

Send comments about this topic to Microsoft