cvs commit: modperl-2.0 STATUS
stas2003/02/19 16:41:51 Modified:.STATUS Log: need to resolve the issue with END blocks Revision ChangesPath 1.34 +5 -1 modperl-2.0/STATUS Index: STATUS === RCS file: /home/cvs/modperl-2.0/STATUS,v retrieving revision 1.33 retrieving revision 1.34 diff -u -r1.33 -r1.34 --- STATUS15 Jan 2003 05:22:53 - 1.33 +++ STATUS20 Feb 2003 00:41:51 - 1.34 @@ -50,6 +50,10 @@ Needs Patch or Further Investigation: - +* child processes never run END blocks. a good example is + Apache::TestUtil, which doesn't cleanup files and dirs it has + created, because the END block is not run. + * Currently modperl_filter_add_{connection|request} check the filter handler function attrs before accepting the filter. If the module wasn't preloaded the check fails and filter handler is skipped. We
cvs commit: modperl-2.0 STATUS
stas2003/01/14 21:22:53 Modified:.STATUS Log: an issue to resolve Revision ChangesPath 1.33 +8 -1 modperl-2.0/STATUS Index: STATUS === RCS file: /home/cvs/modperl-2.0/STATUS,v retrieving revision 1.32 retrieving revision 1.33 diff -u -r1.32 -r1.33 --- STATUS11 Jan 2003 04:14:55 - 1.32 +++ STATUS15 Jan 2003 05:22:53 - 1.33 @@ -50,6 +50,13 @@ Needs Patch or Further Investigation: - +* Currently modperl_filter_add_{connection|request} check the filter + handler function attrs before accepting the filter. If the module + wasn't preloaded the check fails and filter handler is skipped. We + could have this issue documented (which is OK, but might raise too + many questions), but we could also always preload the filter + handlers. To test see TestFilter::input_msg + * we still have a problem with mod_perl starting from a vhost. consider the following config:
cvs commit: modperl-2.0 STATUS
dougm 2003/01/01 10:43:51 Modified:.STATUS Log: must be fixed before 1.99_08 Revision ChangesPath 1.28 +3 -5 modperl-2.0/STATUS Index: STATUS === RCS file: /home/cvs/modperl-2.0/STATUS,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- STATUS1 Jan 2003 03:45:54 - 1.27 +++ STATUS1 Jan 2003 18:43:51 - 1.28 @@ -24,11 +24,9 @@ Release Showstoppers: - - * - Report: - Status: - + * current cvs does not work with vanilla 5.6.1 or 5.8.0 (CGI.pm version issue) + * Makefile.PL process ugly unknown typemap warnings must go away Available Patches: --
cvs commit: modperl-2.0 STATUS
ask 2002/10/10 01:10:41 Modified:.STATUS Log: note crypt() problem Revision ChangesPath 1.15 +8 -1 modperl-2.0/STATUS Index: STATUS === RCS file: /home/cvs/modperl-2.0/STATUS,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- STATUS7 Oct 2002 02:44:30 - 1.14 +++ STATUS10 Oct 2002 08:10:41 - 1.15 @@ -66,6 +66,13 @@ Open Issues or Core Enhancements: - +* crypt() problem: + crypt() seems to give weird return values under mod_perl 2.0: + Message-ID: [EMAIL PROTECTED] + Message-ID: [EMAIL PROTECTED] + Message-ID: [EMAIL PROTECTED] + + * PerlPreConnectionHandler's modperl_callback_pre_connection is not implemented
cvs commit: modperl-2.0 STATUS
stas2002/08/15 08:22:02 Modified:.STATUS Log: add several from the many outstanding issues Revision ChangesPath 1.6 +24 -2 modperl-2.0/STATUS Index: STATUS === RCS file: /home/cvs/modperl-2.0/STATUS,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- STATUS21 Jun 2002 22:25:48 - 1.5 +++ STATUS15 Aug 2002 15:22:02 - 1.6 @@ -31,11 +31,21 @@ -- * Fixing Apache-warn(foo) - Report: Message-ID: [EMAIL PROTECTED] + + Report: http:[EMAIL PROTECTED] + Thread: http://mathforum.org/epigone/modperl-dev/noxtramcay Status: pending Apache::Log compat issues, this and other methods might be dropped. +* The Apache::Scoreboard XS implemenation with tests is awaiting to be + committed + + Report: http:[EMAIL PROTECTED] + Status: waiting for Doug's review + + + * Report: Status: @@ -70,9 +80,21 @@ +* we need a bug reporting utility that can be used post-install, which + should be similar to t/REPORT + + Report: http:[EMAIL PROTECTED] + thread: http://mathforum.org/epigone/modperl-dev/staiblirroo + Status: +1: Stas, Doug + needs to be implemented + + + * Report: Status: + + Documentation: --
cvs commit: modperl-2.0 STATUS
stas2002/06/20 11:31:16 Modified:.STATUS Log: log the Apache::Log issues for a future resolution Revision ChangesPath 1.4 +43 -7 modperl-2.0/STATUS Index: STATUS === RCS file: /home/cvs/modperl-2.0/STATUS,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- STATUS4 Jun 2002 13:01:20 - 1.3 +++ STATUS20 Jun 2002 18:31:16 - 1.4 @@ -4,9 +4,10 @@ Release: - 1.99_03-dev: In development - 1.99_02-dev: Released June 01, 2002 - 1.99_01: Released April 06, 2002 + 1.99_04-dev: In development + 1.99_03-dev: Released Jun 16, 2002 + 1.99_02-dev: Released Jun 01, 2002 + 1.99_01: Released Apr 06, 2002 === @@ -28,6 +29,15 @@ Available Patches: -- +* Fixing Apache-warn(foo) + Report: Message-ID: [EMAIL PROTECTED] + Status: pending Apache::Log compat issues, this and other methods + might be dropped. + + +* + Report: + Status: Needs Patch or Further Investigation: - @@ -36,6 +46,32 @@ Open Issues or Core Enhancements: - +* Apache::Log compat issues: + + Apache-warn, Apache::warn, Apache::Server-warn and + Apache-Apache::Server-log_error are all doing: + s = modperl_global_get_server_rec(); + and this function is thread safe only during the startup. + + possible solutions: + + 1) enforce that these functions are used only at the server startup + + 2) require +GlobalRequest, which gives us r-server, now thread + safe (though slow). + + 3) drop them all from the API and move to compat. + [remember that Apache::warn is needed for registry scripts to + override warn()] + + Report: Message-ID: [EMAIL PROTECTED] + Status: img alt=Doug, contemplating + + + +* + Report: + Status: Documentation: -- @@ -44,7 +80,7 @@ Patches unlikely to be applied: --- - * - Report: - Status: +* + Report: + Status:
cvs commit: modperl-2.0 STATUS
stas02/05/19 02:28:06 Added: .STATUS Log: start the STATUS file Revision ChangesPath 1.1 modperl-2.0/STATUS Index: STATUS === mod_perl 2.0 STATUS: -*-text-*- Last modified at [$Date: 2002/05/19 09:28:06 $] Release: 1.99_02-dev: In development. 1.99_01: Released April 06, 2002 Release Showstoppers: - * Report: Status: Available Patches: -- Needs Patch or Further Investigation: - Open Issues or Core Enhancements: - Documentation: -- Patches unlikely to be applied: --- * Report: Status: