difference SF TWAIN vs. SF Photoshop module

[LSI_Support]

What exactly is the difference / advantage in using either the one or the other SF module?
Advantage SilverFast TWAIN: this SF module is independent of the host application used, it can be launched through all TWAIN-supporting image processing application (as well as various TWAIN-supporting non-image processing applications - OCRs, text processing apps, etc.)
Advantage SF Photoshop: featuring "matching-by-host". Imagine you work in SilverFast (or any other scan application) and you judge your future scan by the scan-preview that you see.
Problem: SilverFast TWAIN module preview looks good, but the final scan into host application differs in colour (hue saturation).
Here is where "matching-by-host" makes the difference:
TWAIN does not adapt a scan preview to the color space used in the host application ? no "matching-by-host? with TWAIN! Therefore, such a "surprise" may occur when the RGB color space used in the host application is rather small and will cut down the colours due to a smaller variety of colour values defined in that working colour space. The result is a different screen display, and output becomes a game of chance.
Not so with SilverFast Photoshop plugin, as this module uses the working colour space of Photoshop as early as in the SilverFast preview display. This ensures WYSIWYG results.

[President_LSI]

Another advantage of the Adobe Photoshop Plug-in technology is the possibility to use functions of the host. SilverFast is using the CMYK-Softproof function of Photoshop to simulate the CMYK proof already on the SilverFast preview. Also the single separations can be monitored on the SilverFast preview.