I haven't done much multi-threading (read: practically none) and was
wondering if anyone would be willing to help me with the design of a simple
multithreaded object.

The purpose is this: I am reading from a "file" (whether it is a
serial port or a pipe or whatever) where information may not be available
"now" but may be later.  I then wanted to put my DosRead calls in
a seperate thread (since I've heard that it can hang if it is in the main
thread, or something like that).  Eventually I'll want to use my own buffer
(probably with semaphore protection) since I'll have to do on-the-fly
transformations (for example, from \n\r or \r\n pairs to \n, as well as
others).  But how do I let the main thread know about what's going on?  Am
I right in assuming that I should use an event semaphore?  Should I then
also use event semaphores for keyboard input, and have the main thread wait
on the mux combination, and then figure out which to process?  Will this
simple design still work if I'm processing input from one or the other
while new input arrives (i.e., will the wait for mux just "fall
through" at that point)?

Any help on getting my mind around multi-threaded programming would be
appreciated (as would any good books on OS/2 multi-threading concepts...
I'm intermediate to advanced for C/C++, but definately novice when it comes
to multi-threading!).

Thanks,


--- Maximus/2 3.01