21 messages in org.apache.httpd.devRe: Is async the answer
FromSent OnAttachments
Akins, BrianJan 18, 2008 10:51 am 
Justin ErenkrantzJan 18, 2008 11:16 am 
Colm MacCarthaighJan 18, 2008 11:20 am 
Akins, BrianJan 18, 2008 11:26 am 
Akins, BrianJan 18, 2008 11:30 am 
Colm MacCarthaighJan 18, 2008 12:07 pm 
Akins, BrianJan 18, 2008 1:16 pm 
Colm MacCarthaighJan 18, 2008 1:28 pm 
Ruediger PluemJan 18, 2008 2:30 pm 
Justin ErenkrantzJan 18, 2008 4:33 pm 
Niklas EdmundssonJan 19, 2008 3:53 am 
Graham LeggettJan 19, 2008 4:45 am 
Davi ArnautJan 19, 2008 6:57 am 
Jim JagielskiJan 19, 2008 7:04 am 
Graham LeggettJan 19, 2008 8:01 am 
Henrik NordströmJan 19, 2008 1:14 pm 
Henrik NordströmJan 19, 2008 1:19 pm 
Davi ArnautJan 19, 2008 3:29 pm 
Graham LeggettJan 20, 2008 7:44 am 
Akins, BrianJan 22, 2008 10:03 am 
Akins, BrianJan 22, 2008 10:07 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Is async the answerActions...
From:Jim Jagielski (ji@jaguNET.com)
Date:Jan 19, 2008 7:04:05 am
List:org.apache.httpd.dev

On Jan 18, 2008, at 2:16 PM, Justin Erenkrantz wrote:

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.

+1... Although the whole concept of buckets and their brigades has some cool advantages, they are also a semi-constant source of issues...