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 paul@querna.org designates
 209.85.210.198 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <C678F60F.C2C1A%Brian.Akins@turner.com>
References: <cc67648e0907070718o375caf30p5f4af5ae0417a186@mail.gmail.com>
	 <C678F60F.C2C1A%Brian.Akins@turner.com>
Date: Tue, 7 Jul 2009 12:57:03 -0400
Message-ID: <4239a4320907070957u2adb48b8l6023ecd6ae4b55be@mail.gmail.com>
Subject: Re: Events, Destruction and Locking
From: Paul Querna <paul@querna.org>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 7, 2009 at 12:54 PM, Akins, Brian<Brian.Akins@turner.com> wrote=
:
> This is how I envisioned the async stuff working.
>
> -Async event thread is used only for input/output of httpd to/from networ=
k*
> -After we read the headers, we pass the request/connection to the worker
> threads. =C2=A0Each request is "sticky" to a thread. =C2=A0Request stuff =
may block,
> etc, so this thread pool size is configurable and in mod_status, etc.
> -any "writes" out of the request to the clientare passed into the async
> thread. =C2=A0This may be wrapped in filters, whatever.
>
> *We may allow there to be multiple ones of these, ie one for proxies, or
> have a very well defined way to add watches to this.
>
> This is a very simplistic view. =C2=A0I was basically thinking that all c=
onn_rec
> "stuff" is handled in the async event thread, all the request_rec "stuff"=
 is
> handled in the worker threads.

Right, but I think the 'waiting for X' while processing is a very
important case, it can get you to a fully async reverse proxy, which
opens up lots of possibilities.