Well, I know that sometimes, I want to force the application to reset. I think that the modification change on the global.asa is a good, not-happen-normally sort of event. If this file has changed, we want to do SOMETHING. I think that the changing of this file should terminate the application - run the old application_onend if you like, even all the session_OnEnd's (yes, I think all the sessions should terminate too) Particularly in development, being unable to triggur this OnStart event without jumping through hoops is very fustrating. And If I do make a change to this central file, I want its changes to take effect immediately.
I could tie Application_OnStart to the recompilation of global.asa, but I would not make the sessions reset too so as to not change this behavior that people may be relying on. I am not worried about changing how Application_OnStart is triggered because it largely useless now anyway. Regardless, I should try to emulate the standard ASP way of triggering these events and fix whatever differences there are.
The way to make everything reset in development is to simply delete everything in StateDir.
Thats okay, but thats not whats happening. When THAT happens, everything is cool. I'm saying, my application data vanishes, when I have active sessions!
I am not sure about this problem you are having. The $Application data should persist so long as your sessions are active.
But I think I know what happened in perspective of StateDir... more than one global.asa set of sub-sessions pointing to the same statedir could result in one application clearing out the application object as it Application_OnStarts... and the other application just has its server/application file cleared out, so its tied value is gone.
Yes? No? Possible ?
As long as some session is active in StateDir, I would not think that $Application would be reset. Perhaps if the global.asa in each application were doing something different with $Application that could affect the shared data in StateDir.
Hmm. Allow me to clarify. I have data, various parts of which need to be available for various scripts. It may be updated. Not regularly or frequently, but *while* the application is running. I don't think a compile-time read-and-load will be appropriate, because I'd have to initiate recompile somehow in order to update the data in memory.
You can re-read the data in Script_OnStart only when it has changed, or you can re-read it in Script_OnStart each request for ease of development & optimize it later. If you do this, its probably better to read the data into a global variable declared like:
use vars qw($DATA);
Regards,
Josh ________________________________________________________________ Josh Chamas, Founder phone:925-552-0128 Chamas Enterprises Inc. http://www.chamas.com NodeWorks Link Checker http://www.nodeworks.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
