www/apache
1
0
Fork 0
mirror of https://github.com/apache/httpd.git synced 2025-08-01 07:26:57 +03:00
Code Activity

- clarify wording on handling of empty brigades, see dev@ thread from

Browse Source 
msgid <AANLkTimaQNuUnDhhL0yoBJXNWS0c163HUWM9WHZhmFLh@mail.gmail.com>


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@950583 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Joe Orton
2010-06-02 14:53:07 +00:00
parent fdcca646fa
commit 3880cb99d4
2 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/manual/developer/output-filters.html.en
View File

@ -120,8 +120,11 @@
ignored.</p>
<p>An output filter should never pass an empty brigade down the
filter chain. But, for good defensive programming, filters should
be prepared to accept an empty brigade, and do nothing.</p>
filter chain. To be defensive, filters should be prepared to
accept an empty brigade, and should return success without passing
this brigade on down the filter chain. The handling of an empty
brigade should have no side effects (such as changing any state
private to the filter).</p>
<div class="example"><h3>How to handle an empty brigade</h3><p><code>
apr_status_t dummy_filter(ap_filter_t *f, apr_bucket_brigade *bb)<br />

7
docs/manual/developer/output-filters.xml
View File

@ -114,8 +114,11 @@
ignored.</p>
<p>An output filter should never pass an empty brigade down the
filter chain. But, for good defensive programming, filters should
be prepared to accept an empty brigade, and do nothing.</p>
filter chain. To be defensive, filters should be prepared to
accept an empty brigade, and should return success without passing
this brigade on down the filter chain. The handling of an empty
brigade should have no side effects (such as changing any state
private to the filter).</p>
<example><title>How to handle an empty brigade</title>
apr_status_t dummy_filter(ap_filter_t *f, apr_bucket_brigade *bb)<br />