IFS LSP
Since this LSP provides the Winsock client application a valid operating system (OS) handle, the particular LSP does not have to implement all the LSP functions, but merely the single one it demands – which in turn is usually a profit. Yet, the negative aspect is that an IFS LSP can’t intercept asynchronous procedures and overlapped operations, such as when WriteFile & ReadFile are utilized together with the IFS handle.
Non-IFS LSP
Due to the fact a Non-IFS LSPwill translate the IFS handles, it must then implement all of the LSP procedures. In the unfortunate event it does not do so, untranslated handles could then reach the operating system (OS) API and result in an error, mainly because the Operating-System is unaware of these kinds of synthetic handles.
A single particular gain of this LSP would be the capability to intercept each and every IFS function that makes use of this socket handle (for instance WriteFile/ReadFile). And another benefit may be the certain ability to collect these notifications from the asynchronous mechanisms.
Houdini