Dmitry Beransky wrote:
> 
> Thanks Joshua,
> 
> Sigh, I guess I have to redesign my code.  It hadn't even occurred to me
> that ASP's session management may not be available outside of ASP.  It's a
> shame, though, to have use two different code bases to do essentially the
> same task.  What would be nice if all of ASP's session stuff got moved into
> Apache::ASP::Session which could be used from anywhere.  I think this is
> more efficient, as: 1) the same code can be used in ASPs and perl handlers;
> 2) memory resources are conserved by sharing session data structures; etc.
> 

This is a hard problem to solve, and I'm not sure how to 
do it ... I have thought about it a couple times now, w/o 
clear resolution.  

The only things that the ASP $Session has that Apache::Session
does not is the event handlers, like hooks into Session_OnStart,
Session_OnEnd, Application_OnStart, Application_OnEnd.  

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:  

sub Script_OnStart {
        $Session = &Apache::Session::initcode; 
}

Then your Apache::Session will be available in your ASP scripts
as $Session

Do you really want the events outside the context of ASP ?

-- Joshua
_________________________________________________________________
Joshua Chamas                           Chamas Enterprises Inc.
NODEWORKS >> free web link monitoring   Huntington Beach, CA  USA 
http://www.nodeworks.com                1-562-683-2142

Reply via email to