Skip to Content

Changes for page Concurrency

Last modified by chrisby on 2024/06/02 15:15
From version 1.15
edited by chrisby
on 2023/11/30 21:05
Change comment: There is no comment for this version
To version 1.16
edited by chrisby
on 2023/11/30 21:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -30,7 +30,7 @@
30 30  * **Libraries**: Use the thread-safe collections provided. Use non-blocking solutions if possible. Be aware multiple library classes are not thread safe.
31 31  * **Concepts**: Mutual Exclusion, Deadlock, Livelock, Thread Pools, Semaphore, Locks, Race Condition, Starvation,
32 32  * **Patterns**: Producer-consumer, Reader-Writer
33 -* **Algorithms**: Study common algorithms and their use in solutions. For example, the Dining Philosophers problem.
33 +* **Algorithms**: Study common algorithms and their use in solutions. For example, the Dining Philosophers problem.
34 34  
35 35  ### Watch out for dependencies between synchronized methods
36 36  
... ... @@ -39,7 +39,7 @@
39 39   * **Client-based locking**: The client locks the server, calls all the server methods, and then releases the lock.
40 40   * **Server-based locking**: Create a method in the server that locks the server, calls all the methods, and then unlocks the server. A client can now safely call this new method.
41 41   * **Adapted Server**: Create an intermediate component to perform the lock. This is a variant of server-based locking when the original server cannot be changed.
42 -* **Keep synchronized sections small. **Locks are expensive because they add administrative overhead and delay. On the other hand, critical sections need to be protected. Critical sections are pieces of code that will only run correctly if they are not accessed by multiple threads at the same time. Keeping synchronized sections small avoids both problems.
42 +* **Keep synchronized sections small.** Locks are expensive because they add administrative overhead and delay. On the other hand, critical sections need to be protected. Critical sections are pieces of code that will only run correctly if they are not accessed by multiple threads at the same time. Keeping synchronized sections small avoids both problems.
43 43  
44 44  ### Writing correct shutdown code is difficult
45 45