X-Git-Url: http://git.shiar.net/perl/plp/.git/blobdiff_plain/e11a488e0909da46fd76f05a6aef47305055e43f..5a304009f58fdfc2158e2ebfc9dd0a7f610fabb1:/lib/PLP/FAQ.pod diff --git a/lib/PLP/FAQ.pod b/lib/PLP/FAQ.pod index 7496f54..0630edb 100644 --- a/lib/PLP/FAQ.pod +++ b/lib/PLP/FAQ.pod @@ -38,10 +38,11 @@ long as you do not switch packages). =item How can I make PLP faster? -With mod_perl, PLP is a lot faster than with CGI. CGI scripts execute an -external interpreter, but mod_perl is a Perl interpreter inside Apache. +With mod_perl or FastCGI, PLP is a lot faster than with CGI. +Instead of executing a new perl process for each request, the same interpreter +will serve multiple pages. -=item I already use mod_perl, can I make my scripts even faster? +=item I already run persistently, can I make my scripts even faster? Well, you already have scripts that probably are faster than PHP equivalents, but speed maniacs always want more. Modules are cached, so with a proper module @@ -78,15 +79,15 @@ B the code is executed (at compile-time). =item Why do my C blocks never get executed? -If they are not, you are probably running under mod_perl. The blocks are -executed when the interpreter stops, but the mod_perl interpreter is not exited -after the PLP script has ended. Use C blocks instead. Please note that -C is a normal statement, so you may need a semicolon. +These blocks are executed when the interpreter stops, which only occurs if you +are running as CGI. To catch the exit of a PLP script, use C blocks instead. +Please note that C is a normal statement, so you may need a semicolon. <: PLP_END { :> <: } :> + contents =item Can I disable the error messages?