[EMAIL PROTECTED] wrote: > - Fix the call when the worker thread waits for a connection to use > the new state variable and use mutexes around the cond_wait() call. >
Why do mutex locking/unlocking around the cond_wait()? In the original implementation, the worker thread just locked the mutex once at startup and then let the cond_wait() unlock and re-lock it for each connection. With this new code, we're now doing twice as many lock/unlock operations per request. --Brian
