August 2011
Intermediate to advanced
280 pages
6h 50m
English
We’re interested in concurrency for two reasons: to make an application responsive/improve the user experience and to make it faster.
When we start an application, the main thread of execution often takes on multiple responsibilities sequentially, depending on the actions we ask it to perform: receive input from a user, read from a file, perform some calculations, access a web service, update a database, display a response to the user, and so on. If each of these operations takes only fractions of a second, then there may be no real need to introduce additional flows of execution; a single thread may be quite adequate to meet the needs.
In most nontrivial applications, however, these operations ...
Read now
Unlock full access