From 632fa0c61ff0b4a2f2c1c6fbee1560fed73ca035 Mon Sep 17 00:00:00 2001 From: Jacob Champion Date: Wed, 4 Jan 2017 00:18:15 +0000 Subject: Some more ideas git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1777250 13f79535-47bb-0310-9956-ffa450edef68 --- STATUS | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) (limited to 'STATUS') diff --git a/STATUS b/STATUS index 290f8270ac..b048a9141f 100644 --- a/STATUS +++ b/STATUS @@ -59,6 +59,8 @@ 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. + * Add performance testing to the test framework. + * Competely untangle core filesystem behavior where a filesystem htdocs/ resource wasn't indicated by the request URI. @@ -115,7 +117,18 @@ THINGS THAT SHOULD BE CONSIDERED EARLY IN THE 2.6/3.0 DEVELOPMENT CYCLE: bias from httpd. * New versioning or release cadence. - + + * Ditch old APIs when we have the chance with 3.x. Consolidate current + functionality into APIs with stronger guarantees. (Specific examples TBD.) + + * Remove as many undesirable-but-kept-for-backwards-compatibility behaviors + as possible from current config directives. (Specific examples TBD.) + + * True event-loop/asynchronous support in the server core. + + * Modify configuration syntax to separate meta-directives from runtime + directives (e.g. If vs. IfVersion). + OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.4 BUT OBVIOUSLY WEREN'T: -- cgit v1.2.1