I forgot to advertise that code for mod_rivet in trunk now builds also for Apache 2.2. I just changed the way the APR thread id is fetched.

Apache controlled threads now allocate data from the thread pool by calling apr_thread_pool_get and set up a clean up procedure to dispose of the resources allocated on that memory (critical points are a mutex and condition variable). I expected this pool to have the same lifespan of the thread that owns it but to my surprise I noticed it's deleted every now and then. This mechanics implies a certain overhead in the request handling as the mutex and condition variable pair used to communicate with the pool of threads have to be recreated every time a single thread's memory pool is recreated.

For the time being I can't figure our a better way to handle this as MPM controlled threads don't have a callback on which you can hook a cleanup procedure

 -- Massimo

---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org

Reply via email to