jim sez: Then we just ship with those... mark any others as
experimental
- * The grammar and interface of ap_expr should be something that we are
- comfortable with keeping for the next few years.
- sf is working on this
-
FOR NEXT ALPHA:
* The mod_session* modules need to be checked that their hooks respect
RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
- * Add mod_allow_method or some other (usable) functionality to replace
- Limit/LimitExcept.
+ * Maybe remove Limit/LimitExcept or at least make it log warnings when
+ mis-used.
* Sort out modules selections for most/all/reallyall. Maybe rename
all -> most, reallyall -> all, and remove the old 'most'.
- Discussion of DBD auth, and, in particular, examples of how to set
up auth using each of the supported databases.
-- Expression syntax for <If> and Require expr
- - Need complete documentation for the expression syntax.
- (Is there any design doc for this? Or do we need to
- read server/util_expr.c?)
- - This should wait until the future of ap_expr is decided.
- See http://mail-archives.apache.org/mod_mbox/httpd-dev/201010.mbox/%3C201010231336.33829.sf@sfritsch.de%3E
+- Expression syntax for <If>, Require expr, SetEnvIfExpr, CustomLog, ...
+ Start is in expr.xml, igalic is working on this
- modules docs
- the follwing modules added since 2.2 lack documentation