Persist the Child Process
In out-of-process filtering, the parent process maintains a persistent connection with the child server after each file is filtered. While 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
In the API
To force the out-of-process server 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:
kvoopRefresh=0
|
When you set |
|
When you set For example, if you set |
When processing a file and an error or timeout occurs, the default out-of-process method does not attempt to process the file again because in most cases this only causes the same error or timeout. This behavior is not configurable. With the legacy out-of-process method, File Content Extraction attempts to process the file one more time, but you can configure the number of retry attempts by setting the kvoopRetry
parameter in the [FilterSDK_Config]
section of the formats.ini
file.
kvoopRetry=0
|
The parent process does not resend the file to a new server. |
kvoopRetry=n
|
The parent process resends the file to a new server n times (where n is a positive number, default 1 ). |