Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of minfrin@sharp.fm designates
 64.49.220.200 as permitted sender)
Message-ID: <49532.196.8.104.27.1162300638.squirrel@www.sharp.fm>
In-Reply-To: <20061031123131.GB12987@redhat.com>
References: <20061030182310.GC25419@redhat.com>
    <5c902b9e0610301036j3de36845rc8767e405def7dd8@mail.gmail.com>
    <20061030204524.78da7f07@grimnir>
    <5c902b9e0610301356l50463afas741558fed01d48@mail.gmail.com>
    <20061031105949.GA12375@redhat.com>
    <19174.196.8.104.27.1162295350.squirrel@www.sharp.fm>
    <20061031120231.GA12987@redhat.com>
    <42934.196.8.104.27.1162296707.squirrel@www.sharp.fm>
    <20061031123131.GB12987@redhat.com>
Date: Tue, 31 Oct 2006 15:17:18 +0200 (SAST)
Subject: Re: cache: the store_body interface
From: "Graham Leggett" <minfrin@sharp.fm>
To: dev@httpd.apache.org
User-Agent: SquirrelMail/1.4.8-2.el4
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

On Tue, October 31, 2006 2:31 pm, Joe Orton wrote:

> To determine writability of the output filter chain is not as simple as
> exposing writability of the socket.  An output filter may block on
> writes because it is blocked on a read from the (writable) socket, this
> happens with SSL for example.

True, but this is not a showstopper. Keep in mind that it's advantageous
to "try very hard" to cache the entire backend as soon as possible, but
this doesn't have to be perfect in every case. If the socket blocks, the
backend is delayed, and we are not as efficient as we theoretically could
be. Oh well.

This doesn't mean it should not try though, and to bring it back to the
store_body() interface, it means store_body() should keep the option open
for this to be possible, via option #1 or #2.

Regards,
Graham
--