> "s there some reason that I shouldn't implement that in a single-threaded > server?"
i don't think there's a general answer for this. the important questions are probablly 1) given how long my program may block gathering a response, is it a problem that all clients block during this time. 2) will i drop events if i'm busy talking to a client? if the answer is "no" to both, why bother with more than one thread? > > you've asked that. i'm not an expert about concurrent programming, i've > never used threads, but here: http://swtch.com/~rsc/thread/ (it's about > that subject) > if you read, you'll see that there that 'block' mechanisms are used to keep > the system synchronyzed, becuase using that block mechanisms keep the system > simple too. > > in systens that you arent going to use concurrent programming, you can do > the synchronization in other ways, more simples, i think. not all threaded programs are created equal. csp is not too bad. locking is subtile and quick to anger. - erik
