Date post: | 01-Jan-2016 |
Category: |
Documents |
Upload: | dara-williams |
View: | 16 times |
Download: | 0 times |
Typical Scenario• Imagine a stockbroker application with a lot of complex capabilities.
One of its functions is "download last stock option prices," another is "check prices for warnings," and a third time-consuming operation is "analyze historical data for company XYZ.“
• In a single-threaded runtime environment, these actions execute one after another. The next action can happen only when the previous one is finished. If a historical analysis takes half an hour, and the user selects to perform a download and check afterward, the warning may come too late to, say, buy or sell stock as a result.
• We just imagined the sort of application that cries out for multithreading.