You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ic...@apache.org on 2016/12/25 16:19:48 UTC
svn commit: r1776014 - /httpd/httpd/trunk/STATUS
Author: icing
Date: Sun Dec 25 16:19:47 2016
New Revision: 1776014
URL: http://svn.apache.org/viewvc?rev=1776014&view=rev
Log:
adding my cents
Modified:
httpd/httpd/trunk/STATUS
Modified: httpd/httpd/trunk/STATUS
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/STATUS?rev=1776014&r1=1776013&r2=1776014&view=diff
==============================================================================
--- httpd/httpd/trunk/STATUS (original)
+++ httpd/httpd/trunk/STATUS Sun Dec 25 16:19:47 2016
@@ -56,6 +56,9 @@ CURRENT VOTES:
THINGS THAT SHOULD BE CONSIDERED EARLY IN THE 2.6/3.0 DEVELOPMENT CYCLE:
+ * Seriously ramp up/replace test framework and cases to have better
+ coverage of existing special cases and behaviours users rely on.
+
* Competely untangle core filesystem behavior where a filesystem htdocs/
resource wasn't indicated by the request URI.
@@ -78,6 +81,11 @@ THINGS THAT SHOULD BE CONSIDERED EARLY I
analysis/attention.
* Better H2 integration?
+ - adding handling of slave connections to mpm, no extra H2 workers,
+ triggering "events" read/write/timer from main/slave
+ - add slave writes/done/abort to events that wake up master connection
+ - disentangle core filters to server one purpose only, so that H2
+ versions can reuse them properly.
* Remove mod_access_compat?
@@ -86,6 +94,18 @@ THINGS THAT SHOULD BE CONSIDERED EARLY I
* Leverage libmill? Drop serf?
* Better abstraction of slave connections and "requests".
+ - add abstraction for "response" as something that can be passed
+ through filters. To be serialized into the correct HTTP bytes on
+ the main connection.
+ - solve multi-threaded access to master connection props/module conf
+ (e.g. ssl vars)
+
+ * make mod_ssl more "core"?
+
+ * add high-level server configuration directives that can steer/influence
+ module defaults/warn/rejects related to security
+
+ * Ditch HTTP/0.9?
OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.4 BUT OBVIOUSLY WEREN'T: