Quote:
Originally posted by some_idiot
quote:
--------------------------------------------------------------------------------
Originally posted by Phil21
Uhm, why don't you figure out what you're talking about before you spout off incorrect crap.
Mod_Perl does *EXACTLY* what he wants, but *IS NOT* CGI. It is not a tool to "embed" perl into html pages, it CAN be used to do that, but is one of those insanely powerful things.
-Phil
--------------------------------------------------------------------------------
Whoa, who pissed in your corn flakes this morning?
Mod_Perl DOES NOT LEAVE THE CODE RESIDENT, it's
an imbedded interupter. EmbPerl is the spec and
Mod_Perl is for embedding Perl into HTML. Geez buddy,
grab your coffee and relax until you can think straight.
Don't you hate it when you act like a jerk and you get
nailed to the wall in public for making stupid statements?
|
Well. Lucky for you this is GFY cause here everybody gets a chance to say stupid things about stuff they don?t have a clue about.
HQ. MOD_PERL will do what you want and more. Same thing about FAST-CGI. They are both aimed at improving the speed of your script execution.
While FAST_CGI is general CGI accelerator MOD_PERL is PERL ONLY.
As any specific target product MOD_PERL might do better for you if you use it correctly - that is if you are using PERL.
MOD_PERL is not for embedding perl into HTML. embed_perl is embedding the mod_perl module into Apache.
MOD_PERL compiles your PERL and stick it into an infinite loop where each call to the original script just releases another execution of the main loop.
Indeed, like Phil21 (who was, compared to some_idiot, at least half right) suggested, you need to know how to "modify" your scripts to MOD_PERL and there is something like global variables BUT unlike he said - dont do the $Blah++ mistake. Its a long technical explanation, but suffice to say, if you do that - you wont get what you expect. at least not the 1, 2, 3, 4, output you might expect.
Unlike some idiot has suggested, MOD_PERL DOES keep the code (compiled version) resident in memory (at least until the original code is modified or Apache is shut down) and that saves both compilation and loading time. Not only does it leave the code in memory, it even leaves multiple instances of it (unless you configure it differently).
In addition it enables you to use Database connection pooling that will accelerate greatly - db centered application.
FAST_CGI works in a different way and also requires special code modification. It works in a manner similar to MOD_PERL but outside the web-server. The disadvantage that FAST_CGI has - is a much smaller user-base than MOD_PERL - hence much smaller "support" group.
Using both like some idiot suggested here - is mostly idiotic (surprise, surprise).
Google "FAST CGI vs. MOD PERL" if you want to learn more.
That?s my
