Geoffrey Young wrote:
Stas Bekman wrote:
since in mp2 the cleanup can be registed on any pool and we have the
following pools: request, connection, server
we could have a perl directive to register a cleanup callback for the
connection callback (of course this can be done from perl already).
Stas Bekman wrote:
since in mp2 the cleanup can be registed on any pool and we have the
following pools: request, connection, server
we could have a perl directive to register a cleanup callback for the
connection callback (of course this can be done from perl already).
people have asked for pe
[EMAIL PROTECTED] wrote:
gozer 2003/03/04 01:42:42
Modified:.Changes STATUS
src/modules/perl modperl_cmd.c modperl_util.c modperl_util.h
t/conf extra.last.conf.in
t/response/TestDirective perldo.pm
xs/tables/current/
Randy Kobes wrote:
On Tue, 4 Mar 2003, Stas Bekman wrote:
Kurt George Gjerde wrote:
On Sat, 1 Mar 2003, Stas Bekman wrote:
There are two ways to debug this if you want to help.
The easy way is to set in httpd.conf
PerlTrace i
as explained here:
http://perl.apache.org/docs/2.0/user/config/confi
since in mp2 the cleanup can be registed on any pool and we have the following
pools: request, connection, server
we could have a perl directive to register a cleanup callback for the
connection callback (of course this can be done from perl already). I don't
think we need one for the server poo
I need good reasons why to do the following
/cgi-bin
*.pm
*.plex files (PerlEX)
*.cgi files
_no subdirectories_
VS
/cgi-bin
*.plex
*.cgi
packages/AMS/
some *.pm files
more directories with other *.pm files
OOP approach
Not quite sure where this one goes, but I know everyo
On Tue, 4 Mar 2003, Stas Bekman wrote:
> Kurt George Gjerde wrote:
> > On Sat, 1 Mar 2003, Stas Bekman wrote:
> >>There are two ways to debug this if you want to help.
> >>
> >>The easy way is to set in httpd.conf
> >>PerlTrace i
> >>as explained here:
> >>http://perl.apache.org/docs/2.0/user/conf
