You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ji...@apache.org on 2007/03/19 16:03:18 UTC

svn commit: r519968 - /httpd/httpd/trunk/docs/manual/developer/output-filters.xml

Author: jim
Date: Mon Mar 19 08:03:17 2007
New Revision: 519968

URL: http://svn.apache.org/viewvc?view=rev&rev=519968
Log:
Note what the actually "valid" usage for apr_brigade_destroy
is, but still urge people to avoid it.

Modified:
    httpd/httpd/trunk/docs/manual/developer/output-filters.xml

Modified: httpd/httpd/trunk/docs/manual/developer/output-filters.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/developer/output-filters.xml?view=diff&rev=519968&r1=519967&r2=519968
==============================================================================
--- httpd/httpd/trunk/docs/manual/developer/output-filters.xml (original)
+++ httpd/httpd/trunk/docs/manual/developer/output-filters.xml Mon Mar 19 08:03:17 2007
@@ -170,7 +170,9 @@
     href="#state">state structure</a>.</p>
 
     <note type="warning"><p>It is generally never advisable to use
-    <code>apr_brigade_destroy</code> to "destroy" a brigade.  The
+    <code>apr_brigade_destroy</code> to "destroy" a brigade unless
+    you know for certain that the brigade will never be used
+    again, even then, it should be used rarely.  The
     memory used by the brigade structure will not be released by
     calling this function (since it comes from a pool), but the
     associated pool cleanup is unregistered.  Using