I use iThreads in productions systems, no ongoing problems (running 2-5 months, ~900k requests)... YMMV.

You'll need to:

• understand the non-shared cloning behaviour
• understand the shared-var clobbering behaviour
• understand where the magic will/won't hold up

I mostly use Thread::Queue to communicate between a reusable pool of threads. I try not to use shared variables (so I don't have to reason about what is/isn't shared). I make sure not to allocate *anything* I don't have to in the "parent" thread.

There certainly are still some problems. There's no other option on Win32; fork() there is an emulation using iThreads which breaks other things (so you shouldn't use it).

I'm sure others will have war stories... I've got what I needed to done without too many problems... mostly working around cloning and file-handle DESTROY issues.

-David