From dev-return-5037-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Wed Dec 05 03:27:55 2001
Return-Path:
Delivered-To: apmail-apr-dev-archive@apr.apache.org
Received: (qmail 30645 invoked by uid 500); 5 Dec 2001 03:27:55 -0000
Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
List-Post:
List-Help:
List-Unsubscribe:
List-Subscribe:
Delivered-To: mailing list dev@apr.apache.org
Received: (qmail 30628 invoked from network); 5 Dec 2001 03:27:54 -0000
Message-ID: <054101c17d3c$cbcec500$93c0b0d0@v505>
From: "William A. Rowe, Jr."
To: "Cliff Woolley" ,
"Justin Erenkrantz"
Cc: "Sander Striker" ,
References:
Subject: Re: Pools rewrite [2]
Date: Tue, 4 Dec 2001 21:27:09 -0600
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-OriginalArrivalTime: 05 Dec 2001 03:27:41.0392 (UTC) FILETIME=[CBCEC500:01C17D3C]
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
From: "Cliff Woolley"
Sent: Tuesday, December 04, 2001 9:12 PM
> > This is my second go at the pools code.
>
> A potential snag with the thread-specific pools idea was brought up today
> when I was talking with FirstBill and some of the others. What is this
> going to do to us a little ways down the road when we try to implement
> async I/O, and all of the sudden requests are jumping from one thread to
> another? Sounds like a big problem if thread-specific pools are in
> place... is there an easy answer?
It certainly better not be a problem, or that asych would be borked.
Only one thread -at-a-time- will be processing a request. Unlike 2.0, there
might be no thread processing a request at a given time, but the request
and connection pools can safely be assumed to be thread-safe at any given
moment, if we do the async right.
Of course, if you implement multi-thread/connection duplexing, then we get
back to the same code we started with. And probably loose most of the
async performance benefits to pool locks.