Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of brianpane@gmail.com designates
 209.85.214.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=D5vmGrPUEpLIu/+koSFm+NN9jAfSaIPdhyKv0IhO4HHrThn8TLUnBhgFTw4b9IwxPN
         X8Fzo0ejwOpZc14qIRgXxeM3nZG/2f/Kbk7gUIHY8hxuXJTJNKlXHRQUm6yW4yLkfFIc
         DgYo8T7w1/JITHtNsfIECb2l5t59MTv7jnv6I=
MIME-Version: 1.0
In-Reply-To: <D84504C8-00AC-421B-84D8-20D6CCF7C379@sharp.fm>
References: <C82EF48D.D10E8%Brian.Akins@turner.com>
 <D84504C8-00AC-421B-84D8-20D6CCF7C379@sharp.fm>
From: Brian Pane <brianpane@gmail.com>
Date: Sun, 6 Jun 2010 05:31:02 -0700
Message-ID: <AANLkTimBFoGbfWPhv2keDEyy9f_2OPVNjUaD4AqLQZgf@mail.gmail.com>
Subject: Re: C as config
To: dev@httpd.apache.org
Content-Type: text/plain; charset=UTF-8

On Sun, Jun 6, 2010 at 5:03 AM, Graham Leggett <minfrin@sharp.fm> wrote:
[...]
> We've also been playing with Varnish, one of the cooler things it does is
> have the ability to suck up an entire response into a RAM buffer and
> releasing the backend before playing out the response to the browser. I've
> looked, and we can do this pretty trivially in httpd as a simple connection
> filter.
>
> Very useful for expensive backends like php, instead of waiting many
> hundreds or thousands of milliseconds for the client to eventually close the
> connection before cleaning up the request pool and release php resources,
> you dump the response into a connection buffer, and destroy the request pool
> asap.

That also would work well with the event MPM; in addition to freeing
up the request pool, you'd be able to free up the request thread.

As long as the documentation explained to users that they need to have
enough memory to accommodate MaxClient * MaxOutputBufferedPerRequest
(where the latter is a hypothetical name for a configurable limit on the
amount of buffered output), such a feature would be a net win for lots
of sites.

-Brian