This module is meant for other parties to use, so I can't define what MPM they use. I would like it to work in either case. I don't mind throwing in locking logic based on the results of querying whether the MPM is threaded or not - I just want to better understand that scenario and how it applies to modules written for mod_perl.
Thanks, SB On Thu, May 20, 2010 at 9:20 AM, Michael Peters <mpet...@plusthree.com>wrote: > On 05/20/2010 08:54 AM, Some Guy wrote: > >> The cleanup handler is a brilliant idea. That removes the need for a >> polling thread. If I attach the cleanup to the request's pool and run >> in a threaded MPM, this led to contention for the globals that I'm >> updating in C. Is this the case with PerlModules, or can I get away >> without locking them? >> > > Why use a threaded MPM? Is there something else you're running that relies > on it? We generally recommend doing with the prefork mpm because you're > running in share-nothing mode which performs better (and uses less memory on > decent operating systems). > > -- > Michael Peters > Plus Three, LP >
