Hi Kee,
thanks for sharing this. I most cases you can use Apache::Reload. This
modules checks on every request which Perl modules have changed and only
reload the changed ones. You could also tell it, at which modules it should
look. This works not in all cases like your solution (e.g. it doesn't
You could just use "do" instead of "use".
Bill
On Sat, 17 Mar 2001, Kee Hinckley wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> (Quite) a while back I complained about the problems of debugging a
> module that's in use by an Embperl page.
>
> [- use mylib; -]
> ...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Quite) a while back I complained about the problems of debugging a
module that's in use by an Embperl page.
[- use mylib; -]
...
The problem is that Embperl cashes mylib the first time it loads it,
and then you start getting really
Yes, this helps...thanks!
Bill
On Sat, 17 Mar 2001, Gerald Richter wrote:
> > sounds to be like the EMBPERL_SESSION_ARGS are stored in global variables
> > that are initialized either at child init time or the first time a request
> is made for that child,
> > and are not reloaded on each execu
>
> Has anyone noticed that sessions are the number one problem in every post
to
> this list?
>
> I know that sessions were my biggest problem with Embperl. I don't care
> what anyone has to say -- they are more difficult to setup than they
should
> be.
>
> Maybe someone who knows them in and out
> sounds to be like the EMBPERL_SESSION_ARGS are stored in global variables
> that are initialized either at child init time or the first time a request
is made for that child,
> and are not reloaded on each execution of the request.
>
EMBPERL_SESSION_CLASSES and EMBPERL_SESSION_ARGS are global,
