Quoting Nicholas Schuetz <[EMAIL PROTECTED]>: > > OK one more thing, I was reading through the Apache::ASP documentation > trying to figure out where I went a stray and here is where I think I got > confused. This is the description for GlobalPackages: > ... > Also, I never had to set the PerlModule Apache::ASP::TYPHOON directive in my > apache conf. I just set the GlobalPackage to Apache::ASP::TYPHOON, defined > my subroutines in global.asa (the global.asa was also in my Global path) and > set the package Apache::ASP::TYPHOON; line in my scripts. > > Am I doing this all wrong or does this list agree that the documentation is > misleading or incorrect? >
Hi Nick, I think you have it right that the documentation needs some revising. What you do *not* need to do is set "package Apache::ASP::TYPHOON" in your scripts, since this happens automatically when GlobalPackage is used. Also, don't ever use the Apache::ASP::* namespace itself. Better in your case to just use the name TYPHOON for the module name. But let's look at the motivation for naming the GlobalPackage namespace for your Apache::ASP application. Perhaps you want to reference a subroutine defined in your global.asa from another module like &TYPHOON::sub(), or perhaps you want to have an actual TYPHOON.pm module that you can load via "use TYPHOON;" whose subroutines you can then access directly from your scripts. It is possible that in your case that you do not even need to use the GlobalPackage setting, and you might try running your application without it. Regards, Josh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
