Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Date: Wed, 14 Mar 2007 18:38:48 +0000
From: Nick Kew <nick@webthing.com>
To: dev@httpd.apache.org
Subject: Re: sed filter module
Message-ID: <20070314183848.14ebd463@grimnir>
In-Reply-To: <20070314165641.GE10745@redhat.com>
References: <0E69D384-8FDE-4242-8383-D96A874D9463@jaguNET.com>
	<20070314143213.GC10745@redhat.com>
	<20070314150153.7b29ec59@grimnir>
	<20070314152743.GD10745@redhat.com>
	<20070314154505.66d0b38b@grimnir>
	<20070314165641.GE10745@redhat.com>
Organization: WebThing
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 14 Mar 2007 16:56:41 +0000
Joe Orton <jorton@redhat.com> wrote:

> On Wed, Mar 14, 2007 at 03:45:05PM +0000, Nick Kew wrote:
> > Nope.  Just one brigades worth at a time.  And the most likely case
> > for that to be an entire document is when it's a static file, and
> > document == brigade == bucket.
> 
> I'm not sure what you're saying here.  Which do you agree with:
> 
> a) size of data represented by a brigade is limited only by apr_off_t

ditto size of a bucket

> b) httpd does use brigades representing large amounts of content e.g. 
> containing FILE or CGI/PIPE buckets

Again, the unit of indefinite size is the bucket

> c) if you loop through all the buckets in a brigade calling read() on 
> every one, you map all the data represented by the brigade into RAM

Indeed.

> d) writing filters which use RAM proportional to content size is bad

Yep.

Now, what leads you to suppose mod_line_edit uses RAM proportional
to content size?  Other than when the entire contents arrive in a
single bucket?

-- 
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/