On 4/18/2010 2:34 AM, alin vasile wrote: > the monitor hook gets only a pointer to an apr_pool_t structure.
Take a look at apr_pool_data_* API's, that should provide you all of the context and persistence you need. You will never see anything about servers, connections or requests because this is running in the *parent*, it is blissfully unaware of specific requests and is therefore immune from being hijaaked by remote code execution and less severe but destabilizing attacks on the request processing code itself.
