I'm making the helper children configurable for on-demand startup so a
minimal set can be started and allowed to grow up to a max as determined
by traffic load.
Growth is triggered by helpers dying or requests needing to be queued
when all helpers are full.
We presently have a default of 5 helpers of each type used started
synchronously on startup and reconfigure.
Are there any objections to making the 3.2 helpers use this on-demand
style by default:
* start 1 child synchronously on start/reconfigure
* new child helpers as needed in bunches of 2
* maximum running kept capped at 5.
?
This affects helpers for auth_param, url_rewrite, and external_acl_type.
Amos
