Advanced Topics in Programming Languages: The Java Memory Model
|
|
|
|
| Articles Reviews Java | |
| Written by Mugur Ingineru | |
| Thursday, 12 April 2007 | |
|
{mos_sb_discuss:34}
The Talk describes the Java Memory Model and what effects the way of concurrent software which should be written. Last changes to the memory model, which they were incorporated into JDK 5, defining the semantics of threads, synchronization, volatile variable and the final fields. The new memory model provides efficient and provably correct techniques for safely and correctly implementing concurrent operations. These techniques are compatible with existing good programming practice, although care needs to be taken in a couple of corner cases. This talk will provide a simple and clear definition of what synchronization actually does, define the semantics of volatile variables and the java.util.concurrent.atomic package (and how they can be used to create efficient concurrent implementations), and describe how final fields can be used to provide thread-safe immutable objects without synchronization. This talk is part of the Advanced Topics in Programming Languages series. {google}8394326369005388010{/google}
{mos_sb_discuss:34} The Talk describes the Java Memory Model and what effects the way of concurrent software which should be written. Last changes to the memory model, which they were incorporated into JDK 5, defining the semantics of threads, synchronization, volatile variable and the final fields. The new memory model provides efficient and provably correct techniques for safely and correctly implementing concurrent operations. These techniques are compatible with existing good programming practice, although care needs to be taken in a couple of corner cases. This talk will provide a simple and clear definition of what synchronization actually does, define the semantics of volatile variables and the java.util.concurrent.atomic package (and how they can be used to create efficient concurrent implementations), and describe how final fields can be used to provide thread-safe immutable objects without synchronization. This talk is part of the Advanced Topics in Programming Languages series.
Powered by jReviews |
|
| Last Updated ( Thursday, 12 April 2007 ) | |
| < Prev | Next > |
|---|







