On 9/11/06, Bojan Smojver <[EMAIL PROTECTED]> wrote:
On Mon, 2006-09-11 at 10:48 -0400, Garrett Rooney wrote:
> If we're going to go
> based off of a NULL pool argument, I'd prefer to allocate out of a
> known to be safe global pool, which we can create as part of
> apr_initialize, then cleanups will happen normally at shutdown time.
OK, no worries.
I guess we can just use the global pool itself, right? We just need to
have mutex to prevent multiple callers from fiddling with the global
pool at the same time. Or maybe such a thing already exists... (haven't
looked at the code yet).
I would prefer to leave the global pool alone, and just create a
separate subpool and mutex around that, since that keeps the global
pool isolated to apr_pools.c, rather than making it accessed from
multiple parts of the source tree.
-garrett
