At 02:50 PM 5/28/2003, Cliff Woolley wrote: >On Wed, 28 May 2003, William A. Rowe, Jr. wrote: > >> It makes me wonder... today we have to create and destroy the pool. >> But what about reuse? The overhead of creating the pool itself? It seems >> like a good extention to the apr_pool api if we had an apr_pool_recycle >> function that would do the usual pool cleanups and frees, but let us reuse >> the pool's own memory without getting tangled in thread locking. For any >> symmetrical use of pools (where each recycle is generally similar in footprint >> to the prior allocations) this could be pretty sweet. > >You can do what you suggest by just doing an apr_pool_clear() and then >reuse the pool, no? There's the max_mem_free thing, but other than >that...
Ok, I was caught unaware :-) Time to refactor some bits of mod_autoindex :-)
