Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Date: Fri, 27 Apr 2001 18:24:34 -0700 (PDT)
From: dean gaudet <dgaudet-list-new-httpd@arctic.org>
To: <new-httpd@apache.org>
Subject: Re: global pools
In-Reply-To: <20010426212947.G921@waka.ebuilt.net>
Message-ID: <Pine.LNX.4.33.0104271822320.26027-100000@twinlark.arctic.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

i suppose pcommands data could be allocated in pglobal instead...

-dean

On Thu, 26 Apr 2001, Roy T. Fielding wrote:

> Once upon a time, httpd would create a global pool as the result from
> alloc_init and use that pool as the parent of almost all of the other
> pools (I say almost only because there is one pcommands pool that was
> separate, though I don't know why).
>
> Now, httpd tells apr to initialize itself and alloc, but doesn't
> get the global pool in return.  httpd then needs to create other
> global pools.  I think this is leading to cases where the proper
> cleanups are not being done, but its a little hard to tell because
> there isn't much in the way of continuity (pools are created in
> subroutines, assumed to exist at a higher level, and then destroyed
> in other places).  Yuck.
>
> Is there some reason that apr can't give us the global pool, or allow
> us to give it the global pool?
>
> ....Roy
>
>