...
| Wiki Markup |
|---|
Consequently, its locking strategy is independent of the locking policy of the {{Book}} instance. This solution incurs a very small performance penalty but the resulting code is much more robust \[[APIGoetz 06|AA. Java References#APIReferences#Goetz 06]\]. |
Risk Assessment
Using client-side locking when the thread-safe class does not commit to its locking strategy can cause data inconsistencies and deadlock.
...