Hi,
what do you think about adding a hook for MPMQ state changes?
AP_MPMQ_STARTING -> AP_MPMQ_RUNNING -> AP_MPMQ_STOPPING
Background: several module monitor the state to abort a loop early to not delay a child exit unnecessarily. However there seems to be no notification mechanism available (or I missed it).
While the cleanup of the child pool is a way to get notified on the exit, some resources may be worth reclaiming at the start of a (graceful) shutdown.
WDYT?
- Stefan
what do you think about adding a hook for MPMQ state changes?
AP_MPMQ_STARTING -> AP_MPMQ_RUNNING -> AP_MPMQ_STOPPING
Background: several module monitor the state to abort a loop early to not delay a child exit unnecessarily. However there seems to be no notification mechanism available (or I missed it).
While the cleanup of the child pool is a way to get notified on the exit, some resources may be worth reclaiming at the start of a (graceful) shutdown.
WDYT?
- Stefan