On Sat, Jul 14, 2001 at 12:10:30PM -0700, [EMAIL PROTECTED] wrote: > On Sat, 14 Jul 2001, Sander Striker wrote: > > The way I see it, each process has a single pool instance as the parent > > for all the threads. Resetting or destroying that pool should effectively > > kill all threads. What am I missing? > > Nothing.
Good, I think we're all in agreement here. Now let's move on to a discussion of how it is currently implemented in httpd and APR. As an application developer, I'd like to see APR's threads more generally applicable (ie. allowing various sms implementations for each thread's pool, but not necessarily forcing all threads to have a child pool). As a [wannabe] contributor to Apache, I'd like to see httpd work. So I have a proposal: APR threads, when created, would now take an additional parameter that is the mechanism (an sms implementation) by which it should create child pools. As it is now, the "pool" that is passed in to apr_thread_create() serves as the "parent" pool for the new thread-specific sms. If this parameter were null, the apr_thread_create() function would not create a sub-pool or register cleanup routines (which satisfies my requirements). Alternatively, the subpool can be already passed into apr_thread_create(), so it doesn't need to know anything about sms, and it leaves it up to the parent to take care of cleaning up the thread when the pool falls out of scope (which is what I was originally proposing). -aaron
