Somehow I think there are not a lot of Win32 programmers on this list... Threads are very safe to use, and in many instances the only reasonable technology to use. A web server without threads? You're not going to serve many customers... And best of all, the OS takes care of spreading the load on multiple processors or, if you have a later generation pentium processor, makes use of the hyperthreading technology.
The only caveat: You have to understand how they work. In that sense you're right when you say it's dangerous to use them if you don't know what you're doing. But that applies to a microwave as well, no? Balthasar Indermuehle Inside Systems GmbH http://www.inside.net "The wireless music box has no imaginable commercial value. Who would pay for a message sent to nobody in particular?" David Sarnoff's associates in response to his urging for investment in the radio in the 1920s. > -----Original Message----- > From: CARIOTOGLOU MIKE [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 15, 2004 18:00 > To: [EMAIL PROTECTED] > Subject: RE: [sqlite] sqliteOsEnterMutex() and sqliteOsLeaveMutex() > > > > > Unsolicited advice: Your best bet is to run no more than > one thread > > in each process. If you need multiple threads, create multiple > > processes to contain them. Writing applications with > multiple threads > > in the same address space is like smoking cigarettes: it > gives you a > > buzz, but in the long run it is deadly. Just say "no". > > > > > > -- > > D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565 > > > that depends on the OS. if you do that in windows, for say, a > web server, you will kill the envrironment pretty soon, as > processes are expensive. it would be fine on Unix, I am told. > >
