21 messages in org.apache.httpd.devRe: Is async the answer
FromSent OnAttachments
Akins, Brian18 Jan 2008 10:52 
Justin Erenkrantz18 Jan 2008 11:16 
Colm MacCarthaigh18 Jan 2008 11:20 
Akins, Brian18 Jan 2008 11:27 
Akins, Brian18 Jan 2008 11:31 
Colm MacCarthaigh18 Jan 2008 12:07 
Akins, Brian18 Jan 2008 13:17 
Colm MacCarthaigh18 Jan 2008 13:29 
Ruediger Pluem18 Jan 2008 14:30 
Justin Erenkrantz18 Jan 2008 16:33 
Niklas Edmundsson19 Jan 2008 03:53 
Graham Leggett19 Jan 2008 04:45 
Davi Arnaut19 Jan 2008 06:57 
Jim Jagielski19 Jan 2008 07:04 
Graham Leggett19 Jan 2008 08:02 
Henrik Nordström19 Jan 2008 13:14 
Henrik Nordström19 Jan 2008 13:19 
Davi Arnaut19 Jan 2008 15:29 
Graham Leggett20 Jan 2008 07:44 
Akins, Brian22 Jan 2008 10:03 
Akins, Brian22 Jan 2008 10:08 
Subject:Re: Is async the answer
From:Justin Erenkrantz (jus@erenkrantz.com)
Date:01/18/2008 11:16:58 AM
List:org.apache.httpd.dev

On Jan 18, 2008 10:52 AM, Akins, Brian <Bria@turner.com> wrote:

Which is why I hate to see a ton of work go into async core if it actually does very little to help performance (or if it hurts it) and makes writing modules harder. It braindead simple nowadays to write well behaved high performance modules (well, mostly) bcs you rarely worry about threads, reads/writes, etc. Full async programming is just as challenging as handling a ton of threads yourself.

Speaking for myself, I think writing and using buckets with serf is more straightforward than our complicated bucket brigade system with mixed push/pull paradigms.

YMMV. -- justin