I just wonder why the global pool ID is "Unknowable". Why did we ever decree that the 'one true root pool' is unknowable to the masses (modules)?
That would be a really sweet place to drop process-lifetime userdata.
You can always create a pool descended from it by passing a NULL parent to apr_pool_create. That will create a separate pool chain outside of httpd's.
But, I really think exposing the global pool would open ourselves to a lot of misuse by modules. Anything allocated in the global pool would never be cleaned up. So, while attaching the userdata information to the global pool might sound nice, I think it opens a can of worms we don't want to open as lots of people may misuse this pool. But, they can already do this if they absolutely must (via pool_create/parent_get, so I doubt we have to make it easier).
As I said before, post_config gets the process pool, so why doesn't pre_config? That seems like the best solution so far. However, that means that we can't backport the mod_ssl changes to 2.0 or we have to come up with another strategy for 2.0. Oh, well. -- justin
