At 09:56 AM 10/25/2002, Mladen Turk wrote: >And finally, the API: > >1. ap_is_one_process() >2. ap_get_parent_id() >3. ap_get_revolution() >4. ap_get_num_childs() > >Thoughts?
First, to -some- degree these sorts of decisions reflect bad architecture. We -should- have provided the hooks so that no decision was necessary. They indicate places where the code will go nutty on a one-off sort of MPM. All that said, they are unavoidable questions today. However, these all belong to the MPM itself. The MPM needs to communicate where you are [a stub parent .exe that won't ever execute client requests, a real parent who's actions are inheritable, etc.] Keep your eye on the MPM design, and also consider using pool data registered against the global process pool to track if you have done some initialization once before, between generations, etc. Bill
