Threads and events are not mutually exclusive. I'm a strong believer in
event-driven programming, but there are times where life is just a lot
simpler when you have two or three threads to play with instead of forcing
everything into one thread. I am definitely NOT of the religion that events
should always be waited for separately, one thread per event.
Mike is, or at least used to be, more thread-happy than me, which is why
I've cc'd him on this message. Thus he could probably argue more
convincingly why Ousterhout is dead wrong. And then I threw Rich on the cc:
list for the heck of it.
At any rate, your homework assignment for tomorrow is to understand and
explain the various COM threading models -- single threaded, multi-threaded,
and mixed. You can start with
http://support.microsoft.com/support/kb/articles/Q150/7/77.asp. It all seems
overly complicated, but I haven't wanted to investigate too deeply because
I've been afraid of finding out that all that complexity was actually
Joseph S. Barrera III <email@example.com>
Phone, Office: (415) 778-8227; Cellular: (415) 601-3719; Home: (650)
Microsoft Research (BARC), 301 Howard Street, San Francisco, CA 94105-6605
The opinions expressed in this message are my own personal views and do not
reflect the official views of Microsoft Corporation.