By 'complex', I am talking about paradigms with names like 'asynchronous programming', 'multi-processing', 'multi-tasking', 'distributed processing', and 'multi-threading'. The general definition for all of these centers around partitioning a task into smaller tasks that are either independent, or parallel, or tightly constrained; and then using a technology (threads, sockets, forks & pipes, shared memory) to stitch them together into a cohesive unit.
Compare the image of yourself fixing a complex dinner, and then imagine 5 10-year old children doing that same job, with yourself standing in the door handing out written instructions to each.
The 'mind set' I first mentioned is the ability to do the partitioning, defining the APIs, understanding the strengths and weaknesses of your selected technology. Then add the understanding of 'critical sections', 'atomic actions', 'shared resources', 'resource locking' and deadly embraces. This part is like turning off the lights in the kitchen, and having a way for the kids to keep the others away from the hot burner or not to reach across the cutting board while someone else is dicing onions.
'Tis better to start with filling 2 glasses with cold water; than to make a holiday meal for an entire family.
In reply to Re: Multithreading, how to?
by Wiggins
in thread Multithreading, how to?
by iSina
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |