> Fair enough. It's just that in order to opt-out of the child-pool creating > process in apr_thread_create, we're going to have to add a parameter Why are we so desperate in opting out the child-pool creation? I don't really have problems with a child pool for each thread. Actually, it will make the dynamic locking a lot easier to implement if it stays. > to the call and that means changing programs that currently using it, > like httpd. > > Would it be nicer to just add new parallel apr_smsthread_create > [name is not > important] functions that do this and allow for the opting-out also? I can > provide a patch for this. Hmmm, the thought of a double interface doesn't bring out happy feelings with me I'm afraid. Sander
- Re: Terminating threads in a process, WA... William A. Rowe, Jr.
- Re: Terminating threads in a process, WA... Aaron Bannert
- Re: Terminating threads in a process, WA... William A. Rowe, Jr.
- Seperating cleanups from memory allocati... Sander Striker
- Re: Seperating cleanups from memory allo... dean gaudet
- Re: Seperating cleanups from memory allo... Aaron Bannert
- Re: Terminiting threads in a process RE: [PAT... rbb
- Re: Terminiting threads in a process RE:... Aaron Bannert
- Re: Terminiting threads in a process RE:... Luke Kenneth Casson Leighton
- Re: Terminiting threads in a process RE:... Aaron Bannert
- Re: Terminating threads in a process, WA... Sander Striker
- Re: Terminating threads in a process, WA... Aaron Bannert
- RE: Terminating threads in a process, WA... Sander Striker
- Re: Terminating threads in a process, WA... rbb
- Re: Terminating threads in a process, WA... Aaron Bannert
- RE: Terminating threads in a process, WA... rbb
- RE: Terminating threads in a process, WA... dean gaudet
- request_rec question Brian Pane
- Re: request_rec question rbb
- Re: request_rec question Ian Holsman
- Re: request_rec question rbb
