Re: async not./canc. (was Re: First in a long line of APR related patches.)

["Roy T. Fielding" <fi...@kiwi.ICS.UCI.EDU>]

>Some of the APR functions will need memory (and yeah, this should be
>minimized, but I don't think it can be avoided). I can think of 4 ways
>to give APR this memory
>
>1. give it pools to allocate it from
>2. let it use malloc/free (what NSPR does)
>3. give APR function pointers to a custom malloc/free
>4. require the caller to preallocate all APR structures before the APR
>   calls are made
>
>I'm happiest with 1 or 4, but I'd think all of them would cause equal
>amounts of added weight. What do you have in mind?

My preference is 4, except for abstract data types specifically designed
to use pools.  This reduces dependencies and allows the caller to use
the same memory for multiple sequential/independent calls.

....Roy