You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ni...@apache.org on 2004/11/07 13:31:27 UTC
cvs commit: httpd-2.0/docs/manual new_features_2_2.xml
niq 2004/11/07 04:31:27
Modified: docs/manual new_features_2_2.xml
Log:
Add info about mod_filter
Revision Changes Path
1.2 +16 -3 httpd-2.0/docs/manual/new_features_2_2.xml
Index: new_features_2_2.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/new_features_2_2.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- new_features_2_2.xml 7 Nov 2004 06:01:50 -0000 1.1
+++ new_features_2_2.xml 7 Nov 2004 12:31:27 -0000 1.2
@@ -47,8 +47,12 @@
<code>Apache JServ Protocol version 1.3</code> used by
<a href="http://jakarta.apache.org/tomcat/">Apache Tomcat</a>.</dd>
- <dt>Smart Filters</dt>
- <dd>...</dd>
+ <dt>Smart Filtering</dt>
+ <dd><module>mod_filter</module> introduces dynamic configuration
+ to the output filter chain. It enables filters to be conditionally
+ inserted, based on any Request or Response header or environment
+ variable, and dispenses with the more problematic dependencies and
+ ordering problems in the 2.0 architecture.</dd>
</dl>
</section>
@@ -100,6 +104,15 @@
set the stack size on all threaded MPMs. This is required
for some third-party modules on platforms with small default
thread stack size.</dd>
+
+ <dt>Protocol handling for output filters</dt>
+
+ <dd>In the past, every filter has been responsible for ensuring
+ that it generates the correct response headers where it affects
+ them. Filters can now delegate common protocol management to
+ <module>mod_filter</module>, using the
+ <code>ap_register_output_filter_protocol</code> or
+ <code>ap_filter_protocol</code> calls.</dd>
</dl>
</section>
</manualpage>