> Under mod_perl, packages/scripts remain in memory across requests, for the
> duration of the Apache child.
> The second issue is that, due to the stateless nature of HTTP, requests are
> dispatched to Apache/mod_perl children at random. You can't store
> information about a particular user or
re (for only this connection)
# than just the value of x.
}
One workaround I imagined was maintaining all the needed state for each
module-session in a database table keyed by sessionid, but I have the hunch
there must be a usual way to do this, and that that's not the way it is.
tia
Collin Monahan
> > I have googled around quite a bit but haven't found anything for
> > this.
> >
> > Using Apache 2.2.3, mod_perl 2.0.2-2.4, both are from Debian
> > packages.
> >
> > I am not using handlers, just scripts, and so I have nothing to
> > shift.
> > Also, the Apache2::requestutil stuff doesn't work
I have googled around quite a bit but haven't found anything for this.
Using Apache 2.2.3, mod_perl 2.0.2-2.4, both are from Debian packages.
I am not using handlers, just scripts, and so I have nothing to shift.
Also, the Apache2::requestutil stuff doesn't work.
$r = shift; # $r will be undefi
