On Wed, 11 Aug 2010, Henning Michael Møller Just wrote: > Jan Dubois wrote: > > Note that you still must make sure all modules used under PerlIS are > > thread-safe because the threads for one application pool all run > > within a single process. So if you have a Perl module with XS code > > that stores information in a static C variable, then you still have > > a race condition when 2 requests are processed in parallel. > > Wowzer. OK, then I've misunderstood the requirements. So basically, if > you are stuck with a module that is *not* thread-safe, you would need > to have it run by old-fashioned CGI, or alternatively, in a PerlEx > pool with only a single interpreter?
Yes, with the further caveat that you should not have additional interpreter classes in the same PerlEx instance either that could load the same module. Maybe that was implied by your statement, but I wanted to make sure nobody tries to create several PerlEx thread pools inside a single IIS application pool, and expect them to be isolated from each other: everything inside a single IIS application pool will happen inside the same process. Cheers, -Jan _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
