>>> [EMAIL PROTECTED] 11/25/02 03:00PM >>>
On Mon, 2002-11-25 at 14:50, Cliff Woolley wrote:
> Well, it just occurred to me that most of the work for doing it
> configurably is already there. There's already a pools-max-free
> directive, so if we just have the pools and the bucket allocator share the
> same apr_allocator_t, we should be golden. That means we need an
> apr_bucket_alloc_create_ex() that takes an existing apr_allocator_t* as a
> parameter. So we set the allocator's max_free first, then create a pool
> that uses that allocator with pool_create_ex, and then create a
> bucket_alloc on the same allocator (and under the same limit) using the
> new bucket_alloc_create_ex.
>
> Sound good?
Makes sense to me.
Brian
On Mon, 2002-11-25 at 14:50, Cliff Woolley wrote:
> Well, it just occurred to me that most of the work for doing it
> configurably is already there. There's already a pools-max-free
> directive, so if we just have the pools and the bucket allocator share the
> same apr_allocator_t, we should be golden. That means we need an
> apr_bucket_alloc_create_ex() that takes an existing apr_allocator_t* as a
> parameter. So we set the allocator's max_free first, then create a pool
> that uses that allocator with pool_create_ex, and then create a
> bucket_alloc on the same allocator (and under the same limit) using the
> new bucket_alloc_create_ex.
>
> Sound good?
Makes sense to me.
Brian
Works for me.
Jean-Jacques Clar
