apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sander Striker" <stri...@apache.org>
Subject RE: Pools rewrite [2]
Date Wed, 05 Dec 2001 11:52:55 GMT
> From: Cliff Woolley [mailto:cliffwoolley@yahoo.com]
> Sent: 05 December 2001 04:12

>> 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?
> --Cliff

The app decides if a pool is thread specific, or put differently, if
a pool will be used only by one thread at a time.  The default behaviour
of the new pools code is to behave the exact same way as the original
pools code.


View raw message