On 4/8/2013 6:11 AM, Gregg Wonderly wrote:
On 4/7/2013 7:03 PM, Greg Trasuk wrote:
I'm honestly and truly not passing judgement on the quality of the
code. I honestly don't know if it's good or bad. I have to confess
that, given that Jini was written as a top-level project at Sun,
sponsored by Bill Joy, when Sun was at the top of its game, and the
Jini project team was a "who's-who" of distributed computing pioneers,
the idea that it's riddled with concurrency bugs surprises me. But
mainly, I'm still trying to answer that question - "How do I know if
it's good?" Here's what I'm doing: - I'm attempting to run the tests
from "tags/2.2.0" against the "2.2" branch. When I have confidence in
the "2.2" branch, I'll publish the results, ask anyone else who's
interested to test it, and then call for a release on "2.2.1" - After
that, the developers need to reach consensus about how to move
forward. Cheers, Greg.
This is an important issue to address. I know a lot of people here
probably don't participate on the Concurrency-interest mailing list that
has a wide range of discussion about the JLS vs the JMM and what the JIT
compilers actually do to code these days.
...
I used to be a concurrency expert, but have not been following the topic
recently. For practical Java coding, I have tended to follow the ideas
in Java Concurrency in Practice. Do any of the changes invalidate that
approach?
Patricia
