This documentation is archived and is not being maintained.

TDI Transports and Their Clients

This section describes the relationship between TDI transport drivers and TDI kernel-mode clients, such as higher level network-interface emulators, redirectors, and servers, that communicate with any transport protocol stack using the system-defined TDI interface.

This discussion includes information about:

  • How PnP-aware TDI transports use device objects to represent their transport-to-NIC bindings.

  • How PnP-aware TDI transports dynamically register network addresses available to clients through these bindings with TDI.

  • How TDI uses file objects to represent network entities.

  • Transport driver dispatch routines required by TDI.

  • Interactions between TDI clients and their underlying transports.

  • Distinctions between TDI requests and events.

This section includes the following topics:

Transport Driver Interface

TDI Device Objects

TDI File Objects

TDI Transport Driver Routines

TDI Kernel-Mode Client Interactions

TDI Requests Versus Events

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