TDI Filter - Is It Nearing Its End?
http://www.webmarktools.net/articles/1608/1/TDI-Filter---Is-It-Nearing-Its-End/Page1.html
Troy Truman
Troy Truman is an online publisher providing great tips on friendly search engine website. To learn more about this topic, visit http://www.NetPointMarketing.com today! By Troy Truman
Published on 02/10/2010
TDI filter is essentially a filtering system that is widely used in Windows NT/2000. This interface is located in between upper level interfaces, which may include Winsock and NetBIOS applications, and the transport layer. Read on to find out more!
TDI filter is essentially a filtering system that is widely used in Windows NT/2000. This interface is located in between upper level interfaces, which may include Winsock and NetBIOS applications, and the transport layer. It can perform server services and as redirector. This interface allows the developer an easy way to program transport protocols because once a protocol is compliant with the TDI interface, it can call on other applications that are on the higher levels.
Other key features of TDI filter is that it can define the process which will be used by transports in notifying clients about any interesting event that occurs in the network. This notification feature does not require the client to comply with any explicit request for I/O. For specific event types like receives and connects, the transport driver interface can also add data along with the notification. This interface also does not have any sanctioned address format. Unlike in NetBIOS where there is a 16-character address requirement for older operating systems, the TDI allows a more flexible way for address formats to be used and identified.
However, it is important to note that TDI filter cannot be used to protect the TCP/IP stack. Besides, the transport driver interface technology is already old in today's standards. With the introduction of Windows Vista, TDI is slowly being replaced by other interface platforms. Windows Vista has a new kernel mode network programming interface that is independent of any transport. Although, TDI will still be supported, it will have significant performance downgrading. In short, the capabilities of this interface will become more limited down the road. To make things more complicated, TDI is not getting any new developments in terms of functionality, which can further clip the wings of this interface platform, so to speak.
Instead of a TDI filter, it is more convenient to use redirectors that allow easy changes into TCP/IP network communications. Third party redirectors can permit a programmer to intercept traffic on the network using customized parameters that he defined. This type of software development kit has many filtering functions that can be used without the need to learn how to write programming codes. Using it gives a programmer total control of which TCP traffic will be redirected so that an inspection can be conducted based on IP, ports, and applications. With this platform, you can also control the UDP traffic that will redirect to Socks5. So, with all these redirector SDK advantages, TDI may be nearing its end.
Other key features of TDI filter is that it can define the process which will be used by transports in notifying clients about any interesting event that occurs in the network. This notification feature does not require the client to comply with any explicit request for I/O. For specific event types like receives and connects, the transport driver interface can also add data along with the notification. This interface also does not have any sanctioned address format. Unlike in NetBIOS where there is a 16-character address requirement for older operating systems, the TDI allows a more flexible way for address formats to be used and identified.
However, it is important to note that TDI filter cannot be used to protect the TCP/IP stack. Besides, the transport driver interface technology is already old in today's standards. With the introduction of Windows Vista, TDI is slowly being replaced by other interface platforms. Windows Vista has a new kernel mode network programming interface that is independent of any transport. Although, TDI will still be supported, it will have significant performance downgrading. In short, the capabilities of this interface will become more limited down the road. To make things more complicated, TDI is not getting any new developments in terms of functionality, which can further clip the wings of this interface platform, so to speak.
Instead of a TDI filter, it is more convenient to use redirectors that allow easy changes into TCP/IP network communications. Third party redirectors can permit a programmer to intercept traffic on the network using customized parameters that he defined. This type of software development kit has many filtering functions that can be used without the need to learn how to write programming codes. Using it gives a programmer total control of which TCP traffic will be redirected so that an inspection can be conducted based on IP, ports, and applications. With this platform, you can also control the UDP traffic that will redirect to Socks5. So, with all these redirector SDK advantages, TDI may be nearing its end.