Communicating sequential processes
Communicating sequential processes
Concurrent programming: principles and practice
Concurrent programming: principles and practice
The SR programming language: concurrency in practice
The SR programming language: concurrency in practice
Distributed operating systems
ACM Computing Surveys (CSUR)
Using Java in computer science education (panel)
Proceedings of the 2nd conference on Integrating technology into computer science education
The Java programming language (2nd ed.)
The Java programming language (2nd ed.)
“Alfonse, wait here for my signal!”
SIGCSE '99 The proceedings of the thirtieth SIGCSE technical symposium on Computer science education
Java resources for computer science instruction
ACM SIGCSE Bulletin
ACM SIGPLAN Notices
Concurrency: state models & Java programs
Concurrency: state models & Java programs
Monitors: an operating system structuring concept
Communications of the ACM
Proceedings of the thirty-second SIGCSE technical symposium on Computer Science Education
ThreadMentor: a pedagogical tool for multithreaded programming
Journal on Educational Resources in Computing (JERIC)
Teaching students to develop thread-safe java classes
Proceedings of the 13th annual conference on Innovation and technology in computer science education
Teaching about threading: where and what?
ACM SIGACT News
| Hi-index | 0.00 |
Synchronization of multiple threads in a Java program using the built-in features of the language has serious pitfalls for the programmer, particularly if a thread is interrupted while waiting inside a monitor. These concerns have lead to a movement to avoid Java monitors altogether and use message passing instead. This paper visits the field of concurrent programming to show that replacing all Java monitors with message passing is an overreaction to these problems.