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 function or a configuration setting.
In the API
To force KeyView to restart, call the fpRefreshFilterKVOOP() function.
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:
When you set |
|
|
When you set For example, if you set |
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:
When you set |
|
|
When you set |
NOTE: The kvoopRefresh
and kvoopRetry
parameters do not apply when you run the File Extraction functions out of process. See Run File Extraction Functions Out of Process.