From: Jeff Trawick <trawick@apache.org>
Date: Wed, 8 Aug 2012 20:10:54 +0000 (+0000)
Subject: conceptual proposals
X-Git-Tag: 2.4.3~92
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f066ae5da79d43ae54ceb178e8a1bf72b42dd173;p=apache

conceptual proposals


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1370931 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/STATUS b/STATUS
index 9c01cec9a9..e33c9e6cb9 100644
--- a/STATUS
+++ b/STATUS
@@ -154,6 +154,23 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
      2.4.x patch: Trunk patch works
      +1: sf, jorton
 
+   * opinions on more complete DefaultRuntimeDir use in 2.4.x?
+     o If a module has no config directive for a run-time file, merge
+       the fix from trunk (via voting on a patch) to respect DefaultRuntimeDir
+       instead of putting it wherever it does currently (generally
+       /tmp or relative to server root).
+       +1: trawick
+     o If a module has a config directive for the run-time file that
+       treats the configured path as relative to server root, preserve
+       that behavior but change the location when not configured to
+       respect DefaultRuntimeDir.  With these changes, users with no 
+       per-runtime-file configuration directives can control
+       everything with DefaultRuntimeDir.
+       BUT: Existing users of DefaultRuntimeDir might get a short-term scare
+       when some unconfigured run-time file starts respecting their 
+       DefaultRuntimeDir directive after an upgrade.
+       +1: trawick
+
 A list of further possible backports can be found at:
     http://people.apache.org/~rjung/patches/possible-backports-httpd-trunk-2_4.txt
 If you want to propose one of those, please still add them here.