You've reached Level 27

"Hi, Amigo!" "Today I will tell you about some things that are convenient when working with loops." "The first is the keyword break. If you use this command in the body of a loop, then the loop will terminate immediately when the command is executed. Here's an example ..."

"Hi, Amigo!"

"Hi, Amigo!" "Today I'm going to tell you what deadlock is." "Hey, you already told me about something like that." "Yep, I did. But today we'll consider the topic in greater detail." "In the simplest case, deadlock involves two threads and two mutex objects. A mutual lock occurs when ..."

"Hi, Amigo!"

"Hi, Amigo!" "I want to tell you about a couple strategies for avoiding deadlocks." "The best strategy is a thoughtful architecture and a set of rules governing when and in what order you can use locks (acquire mutexes). The classic approach to the problem is to develop a lock hierarchy and establish the rule that certain locks can never be acquired in a state where certain other locks have already been acquired ...."

"Hi, Amigo!"

"Hi, Amigo!" "I want to dive deep with you regarding wait-notify. The wait-notify methods provide a convenient mechanism for threads to interact. They can also be used to build complex high-level mechanisms for thread interaction ..."

"Hi, Amigo!" "And a couple more details. Let's call it practical advice." "Suppose you have a method that's waiting for something and falls asleep until a condition is satisfied ..."

"Hi, Amigo!"

"Hi, Amigo!" "There's this huge topic out there—the Java Memory Model. Basically, you don't have to know about it yet, but it will be helpful to hear about it." "To eliminate all potential problems, Java changed its memory management mechanism. Now memory isn't simply divided into a thread's local cache and global memory—the mechanism is even better ..."

"Hi, Amigo!" "Let's continue our lessons on how to google." "Here are some exercises ..."