From: Daniel Ruggeri <druggeri@apache.org>
Date: Thu, 5 Jan 2017 00:25:31 +0000 (+0000)
Subject: Suggestion for STATUS
X-Git-Tag: 2.5.0-alpha~816
X-Git-Url: http://git.ipfire.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=3756339669e4ac6808f3de96862a589c0ac8026a;p=thirdparty%2Fapache%2Fhttpd.git

Suggestion for STATUS

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1777391 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/STATUS b/STATUS
index 2cd212fd00d..cc6f80e89da 100644
--- a/STATUS
+++ b/STATUS
@@ -133,6 +133,13 @@ THINGS THAT SHOULD BE CONSIDERED EARLY IN THE 2.6/3.0 DEVELOPMENT CYCLE:
 
   * Opaque data structures w/ getters/setters 
 
+  * Generic interface to enable runtime changes (adjusting log level, modifying
+    balancer information, toggling flags on/off). Perhaps modules can register
+    callbacks for making these changes?
+
+  * REST-based administration for existing (balancer/etc) and new dynamic
+    runtime changes (see above)
+
 OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.4 BUT OBVIOUSLY WEREN'T:
 
   * Handling of non-trailing / config by non-default handler is broken