Chapter 2

Question 1

synchronization

Answer 1

It includes the use of volatile variables, explicit locks and atomic variables

Question 2

Encapsulation and data hiding

Answer 2

Help you to create thread-safe classes.

Question 3

Thread safe class

Answer 3

A class is thread-safe when it continues to behave correctly when accessed from multiple threads regardles of the scheduling or interleaving of the execution of those threads by the runtime environment, and with no additional synchronization or other cordination on the part of the calling code.

Question 4

Fixing broken thread access

Answer 4

-Dont share the state variable across threads;
-Make the state variable immutable
-Use synchronization whenever accessing the state variable

Question 5

Note

Answer 5

When designing thread-safe classes, good object-oriented techniques — encapsulation, immutability, and clear specification of invariants—are
your best friends.

Question 6

Thread safe class

Answer 6

Thread safe classes encapsulate any needed synchronization so that clients nedd to provide their own.

Question 7

Stateless object

Answer 7

Stateless objects are always thread-safe