Hello,
Everyone is saying that ASP caches pages in memory, but not the compiled
pages. But
I'd like to go straight to the root of the problem and that lies in some C/C++
code. So
here goes:
An Active Scripting Engine has to support many interfaces (thus the way of
COM), one
of those interfaces requires that the Engine have a ParseScriptText method.
What does
this mean? This means that the script passed in is INTERPRETED and STORED (not
executed)
in whatever format the Engine wants. Thus if Mod Perl can store compiled
PerlScript then so
can the Active Scripting Engine. To Actually EXECUTE this code you have to call
another method
GetScriptDispatch. So it is VERY possible depending on how the Scripting Engine
for Perl is
written that ASP+PerlScript can achieve identical results to MOD Perl. And
since VBScript has
less overhead than Perl it is even possible that VBScript runs faster than perl
under ASP.
All this being said, I use Perl+ASP because it is efficient. The only speed
increase you can
probably get is by using the PerlISAPI extensions because they don't have the
internal overhead
of the ASP collections to deal with.
- Justin Rogers, CEO DigiTec Web Consultants
[COOP]DigiTec - Half-Life, Q3A, Unreal Tournament
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
