Persist the Child Process
By default, in out-of-process filtering, the parent process maintains a persistent connection with the child server after each file is filtered. When the connection is preserved in this way, subsequent filtering requests are processed more quickly because the server is already prepared to receive data.
You can restart the server at regular intervals by using a method or a configuration setting.
In the API
To force KeyView to restart, call the refreshFilterKVOOP()
method.
public void refreshFilterKVOOP();
In the formats.ini File
To control whether Filter persists the server, use the kvoopRefresh
parameter in the [FilterSDK_Config]
section of the formats.ini
file:
To control whether the parent process attempts to filter a file after the file has caused the server to fail, use the kvoopRetry
parameter in the [FilterSDK_Config]
section of the formats.ini
file:
The formats.ini
file is in the directory install\OS\bin
, where install
is the path name of the Filter installation directory and OS
is the name of the operating system.
NOTE: The kvoopRefresh
and kvoopRetry
parameters do not apply when running the File Extraction functions out of process. See Run File Extraction Functions Out of Process.