Jeff Trawick wrote:
Occasionally I see problems caused by Apache modules using per-process
pools on a request processing thread. Aside from the thread-safety
issues, they had no business doing that anyway.
apr_pool_lock() - cause abort() on subsequent allocation request
apr_pool_unlock() - allow it to be used again
Although I'm +1 on the subject, the real thing would be
to provide the pool as part of module loading and modle API,
(or two of them) with the same lifetime as pconf, pchild.
Think this would be more safe then forcing users to rewrite
all their modules.
Regards,
Mladen.
