stas2004/10/18 16:19:52
Modified:src/modules/perl modperl_handler.c
Log:
dTHX is never a good idea unless you can't avoid it!
Revision ChangesPath
1.29 +7 -7 modperl-2.0/src/modules/perl/modperl_handler.c
Index: modperl_handler.c
=
stas2004/03/03 15:08:49
Modified:src/modules/perl modperl_handler.c
Log:
verify that GV is valid to avoid segfaults
Revision ChangesPath
1.25 +3 -1 modperl-2.0/src/modules/perl/modperl_handler.c
Index: modperl_handler.c
===
stas2004/02/14 11:23:05
Modified:src/modules/perl modperl_handler.c modperl_mgv.c
Log:
non-ithreaded perl fixes
Revision ChangesPath
1.23 +2 -1 modperl-2.0/src/modules/perl/modperl_handler.c
Index: modperl_handler.c
===
stas2004/02/09 12:35:26
Modified:src/modules/perl modperl_handler.c
Log:
copy the deparsed string before it gets consumed on the scope exit
Revision ChangesPath
1.22 +2 -2 modperl-2.0/src/modules/perl/modperl_handler.c
Index: modperl_handler.c
===
stas2004/02/09 10:19:09
Modified:src/modules/perl modperl_handler.c
Log:
add a xref to where to look at when implementing the '-' prefix
Revision ChangesPath
1.20 +1 -0 modperl-2.0/src/modules/perl/modperl_handler.c
Index: modperl_handler.c
==
stas2003/09/18 00:55:53
Modified:src/modules/perl modperl_handler.c
Log:
mod_perl handler must be dupped for any mpm which runs within USE_ITHREAD.
Untill now there was a big problem with prefork mpm if any of its vhosts
was using PerlOptions +(Parent|Clone) and happened to l
stas2003/09/18 00:51:29
Modified:src/modules/perl modperl_handler.c
Log:
provide a better tracing information, including the pid/tid and the
vhost/port information where relevant
Revision ChangesPath
1.18 +5 -2 modperl-2.0/src/modules/perl/modperl_handler.
stas2003/05/29 00:00:31
Modified:src/modules/perl modperl_handler.c
Log:
since PerlPreConnectionHandler now lives in its own 'desc' struct
(see MP_modperl_handler_desc_* in modperl_hooks.c), we should
use it and not the connection 'desc' struct
Revision ChangesPath
