Manoj Kasichainula wrote: > > On Wed, Aug 14, 2002 at 10:36:53AM -0700, Brian Pane wrote: > > It's not entire libraries that will have to be mutexed, just > > calls to non-thread-safe functions within libraries. That > > will reduce the concurrency of the server, but in general > > not so severely that it's only serving one request at a time. > > Actually, it depends on the library. You could have multiple functions > in a library that all dork with a common bit of non-thread-local state. > > You have to either mutex *all* calls to the library with one big lock, > or examine the library to make sure that it's safe to do less >
Certainly if the threaded lib is bogus, then it's best to avoid the threaded MPM. trying to "emulate" threaded libs by mutexing non-thread-safe libs is pretty nasty. So we are interested in only the n-t-s functions (I would call the multiple functions with commit bit n-t-s) -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson
