At 12:38 PM 10/7/99 , Joshua Chamas wrote:
>If you don't need these event handlers, then you could use
>Apache::Session very well for you needs, as well as ASP $Session,
>then you can turn sessions off in ASP, and set $Session
>to an Apache::Session like:
You're right, I don't currently need event handlers. I was considering
Apache::Session at one point, but then I decided to go with ASP (this was
before I found out that I can't use ASP's session management outside of its
realm). Here are the reasons:
1. Apache::ASP is more of a turn-key solution then Apache::Session
- Apache::Session requires extra steps to set up and
maintain a session id, while Apache::ASP neatly hides
that away.
2. It appears that I will be using ASP quite heavily and while I don't
need event handler now, I may have to start using them in the future.
If that happens, I will have to maintain two sets of session management
code.
well, these were the original reasons...
>sub Script_OnStart {
> $Session = &Apache::Session::initcode;
>}
>
>Then your Apache::Session will be available in your ASP scripts
>as $Session
This is so simple, and, therefore, brilliant! Ok, #2 is taken care of. As
soon as I figure out how to take care of #1, I'm all set.
Thanks!
Dmitry
