I have been reminding everyone, in our graduation design, I have to use a comprehensive comprehensive vision to see the knowledge, data structure, operating system, network, program design, software engineering and other knowledge of the past four years. Less in graduation design is reflected. Today, I remind everyone to study multithreaded problems, how to start. First, what is thread, mention thread, you should think of the process. What is the difference between the two issues, processes and programs, what is the difference and connection between processes and threads? Here, you will remind everyone to learn the association of knowledge, stand in a higher level of thinking about analyzing the problem. Then, you have to ask how your processes and threads are scheduled, what do their life cycles include? If you remember "create", "ready", "run", "block", "demise", etc., think about there are those scheduled algorithms? Some students may ask, why do we want to talk to the principles of OS, pay attention, given a classic principle and algorithm in our textbooks, in your graduation design, especially the design and coding stage, your best teacher It is the knowledge you have learned. Third, why do we design a Java-based chat room to study multithreading? This problem, please think about it. Change an angle to think about it, if you don't have a multi-thread technology, have you designed a defect? Very similar mathematics anti-vision!
