johnli752002 wrote: > Hi, > > I realise that ASP can't store a database handle in $Session as this > isn't shared across processes... > > But, > if Apache 2.0.40 is used > and compiled with the worker mpm > and Apache ServerLimit directive is set to 1 > and Apache ThreadsPerChild directive is set to the number of > concurrent hits you're lightly to see > > (that's a lot of ands) > > Would this result in a single http process with lots of threads that > would be able to share such a handle? >
Theoretically yes. There is a new interface called Apache::TIPool that can create an object that can be shared between threads. I believe this how the windows mpm will be configured to run by default too. > Anyone know if this feasible? Are there any scalability or security > problems? > mod_perl 2.x is still under development, and I have found instability in the worker mpm recently while benchmarking against it. Lots of things do not work yet that used to, like <Perl> sections, but more importantly, modules that we all take for granted like DBI may not be thread safe. I could not even load DBI under worker mpm without it causing the web server to crash oddly. So I would not run it today in production, but I would help the development efforts by trying to get it running and report the bugs that come up for you to the development team. --- from the mod_perl 2.0 readme when reporting bugs please follow the instructions at: http://perl.apache.org/release/docs/2.0/user/help/help.html#Reporting_Problems --- While I think we are a long way off, the worker mpm paradigm shift will be a powerful one, and will allow for things we have never even thought possible before. There will be big performance wins, especially in the memory area. Anything we can do to help the development effort move forward I think we should do. Regards, Josh ________________________________________________________________ Josh Chamas, Founder phone:925-552-0128 Chamas Enterprises Inc. http://www.chamas.com NodeWorks Link Checking http://www.nodeworks.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
