Joshua:
> The notion of application is mostly closely tied to where the global.asa
> resides. This is configured with the PerlSetVar Global config,
> and defaults to '.', the current directory of the executing script.
1) Must all ASP "applications" have a .htaccess file? A message earlier
today suggested that existence of a .htaccess file caused a big performance
hit. If not, can "PerlSetVar Global wherever" be set on a per-directory
basis in the httpd.conf?
2) How can I "localize" variables between different ASP files in the same
application without having to resort to the PerlSetVar UniquePackages 1"?
For example, I have two scripts in the same directory (script1.asp and
script2.asp) that both declare a variable (e.g., "my $filename =
'scrip1.txt'" and "my $filename='script2'"). If ASP compiles these scripts
to the same package, is it possible to ensure that each script doesn't
hammer on the $filename in the other script? If not, is there a "clean" way
to change the "default" package name in the ASP script with having to recode
all subsequent perl (e.g., all $filename references to $NS1::filename and
$NS2::filename.)
More thanks,
JL
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
