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 refreshFilterKVOOP()
method.
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 |
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:
kvoopRetry=0
|
When you set |
|
When you set |