httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Hyde <bh...@pobox.com>
Subject Re: Context types in APR.
Date Fri, 07 May 1999 20:15:39 GMT
Rodent of Unusual Size <Ken.Coar@Golux.Com> writes:

> Ben Hyde wrote:
> > 
> > No?  It would seem to me that you only need to pass a pool
> > to those functions that create objects for the API.
> 	:
> > The case, I assume, your concerned with is when the operation
> > needs scratch space to work in, but that is not returned to
> > the caller.  Apache's standard solution to that has been to
> > store a pool in the object, when it's created, for such things.
> 
> What about the case of apr_os_f(x) that works on strings, not
> APR objects?  Or something that calls apr_os_f(x) under the covers,
> but still appears to only need a string as input?  WHat if there
> *is* no APR object clearly associated with the topmost operation?

I've no problem with passing a pool directly or indirectly to
most functions when there is the slightest chance that over
time they might need our tools.

Since I think the pool has a thread pointer in it for blocking

I don't see what the remaining problem contexts is solving is.

 - ben

Mime
View raw message