Thom Crane wrote: > Please forgive my hastiness to get this problem solved. > I have used require "global.asa" to get my problem worked out, but this > doesn't seem to be the proper way of handling this file from the reading I > have done. > Although not stated explicitly, it has been my feeling from reading at the > site and on this list that global.asa has some higher purpose than just > being another include file.
As dave pointed out, this is where the ASP events definitions reside. However, since the global.asa is also compiled into the same perl package as the rest of the scripts & includes in your application, common subroutines & globals can be defined in there too for use in your application. The trick with getting global.asa to be compiled is your PerlSetVar Global setting needs to point to the location it resides at. If your global.asa resides in the same directory as your scripts, then set Global to . If you would like your $Session & $Application files not stored in ./.state in this case ( the default ), then you can set StateDir to some other directory ( like /tmp/my_asp_app ) > Is using a require the proper way to handle this? If not, would some kind > soul (who has nothing better to do this weekend), please help out a > burgeoning Apache::ASP user with some basics? Doing a require on global.asa has a similar effect, but you should allow for Apache::ASP to reload your global.asa, which it will do correctly whenever you change it. Regards, Josh ________________________________________________________________ Josh Chamas, Founder phone:925-552-0128 Chamas Enterprises Inc. http://www.chamas.com NodeWorks Link Checking http://www.nodeworks.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
