On Oct 13, 2010, at 10:09 AM, Sean Kelly wrote: > I'm not sure if you've read TDPL, but the basic idea is that if thread A > spawns threads B and C, B and C should typically not outlive thread A. > Manual cleanup of spawned threads tends to be messy, so this functionality > was built into the messaging system as the OwnerTerminated exception. So > currently, if a spawned thread should outlive its creator it should receive > OwnerTerminated and ignore it. > > I've added the beginnings of bidirectional linking as well via spawnLinked > and the LinkTerminated exception, so monitor threads can be created to track > the status of worker threads. There is still a lot of functionality missing > however. >
Yes, I have read TDPL. I suppose I don't really care about spawned worker threads outliving owner thread, as long as the owner has a clean way to signal to the worker that it should stop now.
