Micro的soft Layered Service Provider.pptVIP

Agenda LSP – Layered Service Provider in Microsoft Network Architecture Networking API )Windows Sockets (Winsock Remote procedure call (RPC) Web access APIs (HTTP) Named pipes and mailslots Common Internet File System (CIFS) NetBIOS Other networking APIs History of LSP from NT4 till Vista XP SP2 LSP additions From /en-us/library/bb457156.aspx Winsock self-healing Detailed description Winsock, Windows’ network socket facility for applications, is extensible by a mechanism known as a Layered Service Provider (LSP). Winsock LSPs are available for a wide range of useful purposes, including internet parental controls, and web content filtering. In previous versions of Windows?XP, removing a malformed (also known as “buggy”) LSP could result in corruption of the Winsock catalog in the registry, potentially resulting in a loss of all network connectivity. Winsock now has the ability to self-heal after a user uninstalls such an LSP. Two new Netsh commands are available in Windows XP Service Pack netsh winsock reset catalog This command resets the Winsock catalog to the default configuration. This can be useful if a malformed LSP is installed that results in loss of network connectivity. While use of this command can restore network connectivity, it should be used with care because any previously- installed LSPs will need to be re-installed. Netsh winsock show catalog This command displays the list of Winsock LSPs that are installed on the computer. /lsps.html IFS and Non-IFS LSP Pros and Cons of IFS based LSP Pros : IFS LSP base on the handles built for it by BSP. IFS LSP code is much less complicated than non-IFS LSP. It does not need to handle the various complicated I/O models associated with WSPAsyncSelect and overlapped I/O since an IFS LSP cannot be on the completion path of I/O operations. Secondly, an IFS LSP only needs to implement those Winsock SPI functions that