Caroline’s Reviews > Java Concurrency in Practice > Status Update
Caroline
is on page 319 of 432
Chapter 14 - I already understood condition variables, but it was interesting to see how they work in Java. The AbstractQueuedSynchronizer was new to me. I don't think I could use it solely based on the info in this book, though.
— May 13, 2019 04:26PM
Like flag
Caroline’s Previous Updates
Caroline
is on page 353 of 432
Chapter 16 - One of these days, I should read the actual Java memory model. But in the meantime, having a nice summary was helpful.
— May 15, 2019 02:57PM
Caroline
is on page 337 of 432
Chapter 15 - The lock-free queue algorithm presented here was fascinating.
— May 14, 2019 02:38PM
Caroline
is on page 291 of 432
Chapter 13 - I didn't really understand explicit Lock objects in Java before. Good to know, I guess. Although honestly I really love Java's synchronized keyword.
— May 10, 2019 04:30PM
Caroline
is on page 247 of 432
A lot of this was stuff I knew or common sense. Still, I have a feeling I'll be coming back to this chapter if I'm ever seriously trying to improve the performance of a concurrent program.
— May 06, 2019 05:38PM
Caroline
is on page 221 of 432
Chapter 10 - Interesting contrast of Java with database systems. I usually take it for granted that deadlock will be unrecoverable, but it's a good point that there are real world systems that very often recover! The pattern of "open calls" also sounds very useful and is not something I had considered before.
— Apr 30, 2019 02:50PM
Caroline
is on page 203 of 432
Chapter 9 - "If you've tried to write even a simple GUI application using Swing..." No, I haven't. Maybe I should have skipped this chapter.
— Apr 26, 2019 04:01PM
Caroline
is on page 189 of 432
Chapter 8 - Very interesting, although not as relevant if you're used to working with higher level third party execution frameworks instead of managing your own thread pools.
— Apr 26, 2019 03:08PM
Caroline
is on page 167 of 432
Chapter 7 - I've spent surprisingly little time in my career making sure the programs I write are responsive to cancellation. Still, it's interesting to know the intention behind InterruptedException. I have to wonder about the design choice, though, since it forces every program to handle InterruptedException even though many might not care about supporting cancellation. What a pain.
— Feb 15, 2019 04:08PM
Caroline
is on page 135 of 432
Chapter 6 - This is a very useful chapter. ExecutorService is a must have for concurrent code, and the chapter clearly explains why.
— Feb 06, 2019 06:26PM

