This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
programs:odxnet:home [2009/12/07 00:07] tdo |
programs:odxnet:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 301: | Line 301: | ||
| If an ODXNET configuration file is not used, pooled processes for the different application types will be created when the ODXNET listener is started, using default settings, unless the -nopools option is used. In which case, no processes will be started and no connections will be opened to any Omnidex environments until a client request is received. However, client connection times can be greatly reduced by using a waiting process, therefore, we do not recommend using the -nopools option unless specific application needs require it. | If an ODXNET configuration file is not used, pooled processes for the different application types will be created when the ODXNET listener is started, using default settings, unless the -nopools option is used. In which case, no processes will be started and no connections will be opened to any Omnidex environments until a client request is received. However, client connection times can be greatly reduced by using a waiting process, therefore, we do not recommend using the -nopools option unless specific application needs require it. | ||
| - | + | ==== Pooled Process Configuration ==== | |
| - | ===== OdxNet Configuration ===== | + | |
| Configuring pooled processes is done in the ODXNET configuration file. | Configuring pooled processes is done in the ODXNET configuration file. | ||