stas 2004/02/27 11:25:05
Modified: todo release
Log:
mark items that I work or plan to work on
also mark a few of the things tha gozer is working on/planning to
Revision Changes Path
1.18 +16 -10 modperl-2.0/todo/release
Index: release
===================================================================
RCS file: /home/cvs/modperl-2.0/todo/release,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -u -r1.17 -r1.18
--- release 12 Feb 2004 02:05:29 -0000 1.17
+++ release 27 Feb 2004 19:25:05 -0000 1.18
@@ -5,6 +5,18 @@
* some autogenerated record accessors shouldn't be get/set but only get (e.g.
Apache->server->is_virtual(1) is wrong). Need to add a new flag supported by
MapUtil and map files, where we can say which accessors should be read-only
+ owner: stas
+
+* Apache::{Server,Process} classes:
+ require mutex lock for writing (e.g. $s->(error_fname|error_log)
+ Status: most likely some server/process datastructures aren't
+ supposed to be modified at request time. So instead of mutex
+ locking, we think we should simply have a flag that will be down
+ during the startup and will allow methods modifying $s/$proc structs
+ (the method will check that flag and if it's up it'll die). At the
+ beginning of child_end it'll raise the flag and lower it at the end
+ of child_exit.
+ owner: stas
* static build - if we make it working on OpenBSD, AIX and FreeBSD,
then it's not important to fix the DSO issues, otherwise make the
@@ -13,6 +25,7 @@
could probably try to re-use some of the code that was written to do
that, though they use autoconf, which is not quite what we
want. Anyway it's something to look at.
+ owner: gozer
* META.yml. Generate META.yml (make dist does that), add Apache-Test
as a private resource, so it won't be attempted to be indexed by
@@ -22,6 +35,7 @@
* <Perl> sections:
A few issues with <Perl> sections:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=106074969831522&w=2
+ owner: gozer
* Fixing Apache->warn("foo")
@@ -38,12 +52,14 @@
Apache::TestUtil, which doesn't cleanup files and dirs it has
created, because the END block is not run.
also: see the next item
+ owner: stas
* ModPerl::Registry END {} block woes , described in details at the
forwarded message from Jim Schueler
http://marc.theaimsgroup.com/?l=apache-modperl&m=103720834717981&w=2
the whole thread is here:
http://marc.theaimsgroup.com/?t=103713532800003&r=1&w=2
+ owner: stas
- PerlModule, PerlRequire, <Perl> in .htaccess is missing
http://marc.theaimsgroup.com/?t=105370088700001&r=1&w=2
@@ -83,16 +99,6 @@
several versions, like mod_perl 1.0 and mod_perl 2.0, since once we
release it any dependency on mod_perl will be resolved as mod_perl
2.0, when mod_perl 1.0 may be required instead.
-
-* Apache::{Server,Process} classes:
- require mutex lock for writing (e.g. $s->(error_fname|error_log)
- Status: most likely some server/process datastructures aren't
- supposed to be modified at request time. So instead of mutex
- locking, we think we should simply have a flag that will be down
- during the startup and will allow methods modifying $s/$proc structs
- (the method will check that flag and if it's up it'll die). At the
- beginning of child_end it'll raise the flag and lower it at the end
- of child_exit.
* Apache::Reload
- needs to handle properly redefined subs warnings
