> it seemed safer at first if I didn't have to worry about the procs > preempting each other (and appart from that dial() bottleneck, I don't > need them to), that's why I started with threads. I was thinking of > sticking to threads and not using procs until I really do need them. But > yeah, no real good reason not to switch to procs if that's the best way > to go in that case.
one can use ioproc(2). though i tend to go for procs. this is because i have a hard time understanding why csp (and thus safety) wouldn't generally be used instead. and when csp techniques aren't going to cut it, i find it easier to understand a small amount of explicit locking, because the interesting bits of contention are well-marked. - erik
