IMHO, there are a lot of reasons to bite the bullet and start using a response pool in httpd. It would certainly allow us to improve the memory use of mod_dav (pet peeve of mine). Switching where the brigades are allocated isn't going to help mod_dav at all (due to the way it needs to walk the tree before generating any output). The only proper solution would be a response pool.especially in the case of a proxy. Creating a "response pool" will work, but that doubles the amount of memory that the server must devote to a given request (one pool for request, one for response).
Saying a response pool 'doubles' the memory is an absolute non-starter. Back that up, please. If you're meaning the additional 8kb minimum for the separate pool, I seriously can't believe that's going to be a major concern. How is it going to double the memory when that minimum threshold is exceeded?
A response pool solves the same problem as allocating the brigade from a non-cleanup protected memory allocator, and I believe has better long-term advantages for the overall architecture of httpd. -- justin
