Date: Tue, 14 Sep 1999 09:15:15 -0700 (PDT)
From: Dean Gaudet <dgaudet@arctic.org>
To: new-httpd@apache.org
Subject: Re: Apache using apr.
In-Reply-To: <37D646A3.65AA1ED9@lyra.org>
Message-ID: <Pine.LNX.3.96dg4.990914091410.14162Q-100000@twinlark.arctic.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org


On Wed, 8 Sep 1999, Greg Stein wrote:

> Dean Gaudet wrote:
> > 
> > On Fri, 27 Aug 1999, Greg Stein wrote:
> > 
> > > We should use contexts so that the user data can be carried around. Dean
> > > suggested added a void* to the pool structure. That is a bit silly as
> > > that means pools are no longer just memory handling types, but include
> > > other stuff. The best label to apply for that case is "context".
> > 
> > note if you see my other post about supporting all types of allocation
> > within one pool you'll see that it'd be cool for the different allocators
> > to have a void * that they can allocate within the pool...
> 
> I'm not sure that I follow what you're getting at here. Would the
> allocator use the void* internally? Well, sure... that makes sense. I
> would expect them to have some kind of private storage in there.

i mean the allocator would use the void * provided by the context, the
allocator needs somewhere to hang its private data.

> Or do you mean something about exposing the void* to users? In that
> case, then you're monkeying up the abstraction between allocators and
> context storage.

private. 

Dean