stas 2002/06/20 11:31:16
Modified: . STATUS
Log:
log the Apache::Log issues for a future resolution
Revision Changes Path
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
--- STATUS 4 Jun 2002 13:01:20 -0000 1.3
+++ STATUS 20 Jun 2002 18:31:16 -0000 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:
