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:Akins, Brian (Bria@turner.com)
Date:Jan 18, 2008 11:26:44 am
List:org.apache.httpd.dev

On 1/18/08 2:16 PM, "Justin Erenkrantz" <jus@erenkrantz.com> wrote:

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.

It very well may be.

Async may be easy. Except when my db connection blocks.. On stat calls.. Etc.

I am by no means defending the buckets! Or anything for that matter... Just some observations. I just no longer buy into the idea that async is somehow inherently superior. It sounds good in theory, but in the "real world" I am just not seeing it.

The whole reason I brought this up was to stimulate discussion. I really really would hate for us to spend many months porting everything over to async to discover that it made no positive impact on performance. Worse, it made extending httpd (or "D") much harder.