Henry Jen wrote:
William A. Rowe, Jr. wrote:
Henry Jen wrote:
/**
* Stop all unused threads. Ignore the maximum number of idling threads.
* @return The total number of threads stopped.
*/
APR_DECLARE(int) apr_thread_pool_stop_unused_threads(void);
I'm a little confused in your proposal
Hello all,I'm new to this list, please forgive me for any ignorance I might manifest in my messages.But to get straight to the point, my task is to develop a small tcp server plugin with apr. I'm using a pollset to handle multiple requests and I put together a very simple test system following the
William A. Rowe, Jr. wrote:
Henry Jen wrote:
Hi,
We would like to implement thread pool capability, and think it might
be a good addition to apr-util or apr.
Interesting!
I don't see where your thread join occurs to reap any terminated threads,
that is, how your model handles threads that
On 4/5/06, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:
This has been sitting out a while. Any comments from the vocal majority
on their favorite platform? Seems sane to me, but needs eyes from folks
intimately familiar with the pthreads implementation.
I noticed more are trying to purge
On 4/5/06, Matti Eskelinen [EMAIL PROTECTED] wrote:
Hello all,
I'm new to this list, please forgive me for any ignorance I might manifest
in my messages.
But to get straight to the point, my task is to develop a small tcp server
plugin with apr. I'm using a pollset to handle multiple
Garrett Rooney wrote:
On 4/5/06, Matti Eskelinen [EMAIL PROTECTED] wrote:
As far as I know there is no way to make the pollset code not use
AcceptEx, so you'd have to implement such a thing yourself inside the
pollset code.
As for the potential bug, it would probably be easier for a
Quoting Bojan Smojver [EMAIL PROTECTED]:
Is there are particular reason why PQprepare() isn't used to prepare
statements? Currently, DBD code builds an SQL statement with PREPARE
[...] at the beginning and then executes that, instead of calling the
mentioned API function.
Don't worry about
