John Kubie wrote: >> There are a lot of things to consider when analyzing this problem. > > Thanks, Brendan, you give me a lot to think about. > > Even if I don't get a clear answer, I'm learning a lot. > > One solution I'm considering is not to use a thread at all, which has > benefits and drawbacks. But I want to understand what's going on.
You absolutely correct in saying, "I want to understand what's going on," Having a correct understanding of how RB handles threads and thread issues is important since it can affect the design of the program. Having a general knowledge of what is going on under the hood with thread processing is valuable information and means you can avoid pitfalls with thread programming and use threads in a proper way. For example, knowing when you hit a loop construct you have to consider who's got what resources and who can you modify them through mutexing and critical section code. Sometimes you can use timers to do things that you would do in a thread. So timers can be alternate implementation. Use the right tool for the job or just kind of beat it in with a hammer until it fits. :) _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
